-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
unawaited_futures: False positives -> '.then' #57500
Comments
EDIT: Looks like restarting analysis does "fix" it, temporarily. New warnings are not ignorable until you restart again, though, and it sort of still presents itself as you code/add more. |
Ping. This is really annoying. I'd prefer this fixed before new lints are added if that's reasonable. |
The new lints you are seeing are part of a project trying to add the
readability/effective dart related lints. Once they are added (the machine
verifiable ones of course) some other improvements will be triaged, but so
far we are planning on adding support for those rules in the analysis
server to have the corresponding quick fixes available in intellij and
other editors.
Since this project mostly lives of community contributions, it is a good
idea to reach directly to the author, I believe it to be @ochafik.
|
Where is the quick fix support? That's part of the linter? |
Quick fixes lives in the analysis_server package. |
@bwilkerson - is there a reasonable chance of getting a quickfix that wraps the future with a call to |
I have no problem having such a fix added; it's merely a question of priorities and resources. |
I haven't seen an issue with this. |
This should not trigger a lint warning:
But it does. On top of it, I can't ignore the lint warning at all:
If this can't be fixed I'm request the lint be disabled for the next SDK release.
The text was updated successfully, but these errors were encountered: