-
Notifications
You must be signed in to change notification settings - Fork 65
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
Error when removing Flutter dependencies from pubspec.yaml in specific modules #238
Comments
I had the same error with a slightly different setup and I could solve it.
At first I added
and
Then I noticed that the issues is solved once I ensure that the analyzer plugin is set just once in my root package and not in every I hope this might help you. |
Custom_lint currently does not support modifying dependencies while it is running. If you edit your pubspec.yaml in ways that impact lints, you have to restart custom_lint somehow (such as through restarting your IDE). I don't know a way to solve this in a more convenient way for now, because custom_lint has no way to restart itself. |
Thank you very much. Yes indeed in this variation the linter shows errors. However, fixes inside packages are not available. Are there any options for how to solve this? |
Dependencies do not change during development. This error appears from the start of the IDE, the linter simply cannot start. If necessary, I can provide a repository where there is an opportunity to repeat this error. |
@rrousselGit This bug only appears in Android Studio and in VS Code everything works fine. |
The The other error, I'm unfamiliar with it. So I'd require a specific reproduction for that. |
I have the following structure in a project.
Added to pubspec.yaml for all packages:
And if you remove from one package all dependencies related to flutter, for example domain:
And in other packages I leave everything as is, then I get an error:
Sometimes:
However, this problem is observed only in Android Studio, when using VS Code this problem is not observed
The text was updated successfully, but these errors were encountered: