Skip to content
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

Analyser not picking up changes after BuiltValue generation WebStorm/MacOSx #34344

Open
3 tasks done
rayk opened this issue Sep 3, 2018 · 2 comments
Open
3 tasks done
Labels
analyzer-stability area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. P3 A lower priority bug or feature request type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@rayk
Copy link

rayk commented Sep 3, 2018

This issue started life in BuiltValue, making it was here because its beginning to seem a lot more analyser related. @davidmorgan

Formalities
VM
Dart VM version: 2.0.0 (Fri Aug 3 10:53:23 2018 +0200) on "macos_x64"

IDE
WebStorm 2018.2.3 EAP Build #WS-182.4323.31, built on August 30, 2018 JRE: 1.8.0_152-release-1248-b8 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

  • Checked Stackoverflow
  • Search Previously filled issues.
  • Observable and repeatable symptoms.

Summary

After making changes to a BuiltValue abstract and successfully generating the implementation, Webstrom is unable to detect the generated file, causing the disliked red squiggly line to appear. By manually restarting the analyzer from with the IDE all is made good with the world.

The initial diagnostic and Q&A is here, would appreciate any help. This issue is not a show stopper, yet does interrupt the development flow.

@bwilkerson bwilkerson added area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) labels Sep 3, 2018
@corwinsheahan-wf
Copy link

We're also seeing this issue with over_react. It would be great to not have to restart the analysis server after every build.

@aaronlademann-wf
Copy link

@bwilkerson any updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer-stability area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. P3 A lower priority bug or feature request type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

5 participants