-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Analyzer doesn't notice when (path) dependencies change #54047
Copy link
Copy link
Open
Labels
P2A bug or feature request we're likely to work onA bug or feature request we're likely to work onanalyzer-stabilityarea-dart-modelFor issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.For issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)
Metadata
Metadata
Assignees
Labels
P2A bug or feature request we're likely to work onA bug or feature request we're likely to work onanalyzer-stabilityarea-dart-modelFor issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.For issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)
STEPS TO REPRODUCE
mkdir foocd foodart create -t package the_librarydart create the_programthe_program/pubspec.yamlin thedependenciessection:(cd the_program; dart pub get)(cd the_program; flutter analyze --watch); leave this running in the backgroundthe_library/lib/src/the_library_base.dartinclass Awesome:the_program/lib/the_program.dartwith:EXPECTED RESULTS
There should be one issue:
ACTUAL RESULTS
The error is bogus, because the library being depended on does define
isAmazing.If you restart the analyzer, the bogus error goes away.
IMPACT
This is problematic when developing a package, because any example that relies on the package, which you're probably developing in conjunction with the package, will have to have its analyzer continually restarted.