-
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
analyzer regression on pub.dartlang.org #35732
Comments
In this case, your package is a Flutter plugin, and we use the defaults recommended for new Flutter projects to analyse it: https://github.com/flutter/flutter/blob/master/packages/flutter/lib/analysis_options_user.yaml Last week we've released a new version of pub site that used the updated rules, that's why you see the change. As the recommended defaults change over time, Looking at you code, it seems that you are using the final fields with uppercase, which is usually for classes. As the package is popular, I wouldn't do a single breaking update to it, rather a gradual one:
|
@isoos I see, thanks for the info and the suggestions. I will amend as per your recommendations. Cheers! |
Does |
Not yet, but hopefully we'll get there: |
I guess thats why I've got confused. Moreover the official reference on this topic does not reflect those recent changes, instead it shows the old rules available https://pub.dartlang.org/help#health |
Hi I am the maintainer of https://pub.dartlang.org/packages/multi_image_picker
Until today my package did not had any Health errors. However since today, I've released a new version, and the analyzer on pub.dartlang.org shows those problems:
However locally analyzer does not report any issues as it should be because I haven't included
non_constant_identifier_names
in my confighttps://github.com/Sh1d0w/multi_image_picker/blob/master/analysis_options.yaml
For some reason it seems like pub.darlang.org ignores the package analysis_options and uses its own rules, which is regression from what we had before.
The text was updated successfully, but these errors were encountered: