-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Override analysis_options yaml file with project's #23
Comments
I have the same problem. |
I created PR #20 one month ago to add this feature. Meanwhile you can switch to my branch. |
Will try to build your branch as soon as OpenJDK site resurrect (is currently unreachable) to download OpenJDK 11 which is required to build the plugin. |
Here is the one I'm using : Follow the documentation update to configure it |
Thank you for the help but for security reasons I can't install a JAR which is not coming from a "trusted" source. |
Ok ;) |
I was surprised that the plugin overrides existing I guess the expected behavior would be to use the existing rules, and if there are none, fallback to some default rules (preferably pedantic or effective dart). |
I need this feature. I using pedantic rules, but when run |
You can either use the one I provided a month ago or wait for the maintainer to merge my PR. |
Hi, |
Hi, I'm currently trialling the usage of this plugin to be used in my Flutter project.
There are some rules I would like to leave out of the analysis, such as:
dartanalyzer:prefer_double_quotes
, as we are practicing using single quotes instead.Is there a way (like pass in a flag) to indicate to use our own project dir's analysis options file?
Thanks!
The text was updated successfully, but these errors were encountered: