-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
composeRoot not found error in case of cancelled compose with at least one recipient #756
Comments
I'm not sure I fully understand the scope of this bug. From a API usage point of view, are there use-cases which does not work as expected? |
I think that, in the described use case, it is expected that no composeRoot will be found, so I don't see the point of throwing an error, making you wonder if something is indeed not ok in/with your code. |
In that case, I guess "error" is more severe than it needs to be. But it could be because of something unexpected happening too. How about warning instead of error? |
Yes, that is a good idea. But only for the cases other than compose close(not sure how this case can be identified among the others, but this would be the ideal behavior). |
Feel free to give it a try. PRs welcome 🙂 |
When closing a compose modal, after having added at least one recipient, an error of
Can't find composeRoot for [object Object]
is logged in therecipient_change
event handler:gmail.js/src/gmail.js
Line 2529 in edd1bee
The text was updated successfully, but these errors were encountered: