Hi, there are some packages that scored 0 for health, but they are working properly when included and used.
For instance:
Got the same. I updated the package twice today. First time was fine second time I got the same issue as above.
slide_container: https://pub.dartlang.org/packages/flutter_redux#-analysis-tab-
@quentinleguennec: We had a new release where we've upgraded our Flutter version to 0.10.1. It is possible that the first deploy was on the previous version, and the new one exposes more issues.
@ariedov: the analysis exposed 30+ errors in the package. It is possible that previous Flutter versions were OK using them. Do you know which version are you on?
Got the same with https://pub.dartlang.org/packages/dartea#-analysis-tab-
I'm using Flutter 0.10.1, library is compiling without problems. Tried to use it via pub in fresh projects - everything works fine.
One common thing in these reports I've noticed is the reference to mixins. pana (the analysis library) enables superMixins in the custom analysis-options.yaml we are using. I'm not following Flutter closely, maybe something did change in that area?
@isoos I've tried to run analyzer locally with this options
analyzer:
language:
enableSuperMixins: true
errors:
# treat missing required parameters as a warning (not a hint)
missing_required_param: warning
# treat missing returns as a warning (not a hint)
missing_return: warning
# allow having TODOs in the code
todo: ignore
# Source of linter options:
# http://dart-lang.github.io/linter/lints/options/options.html
linter:
rules:
- camel_case_types
- hash_and_equals
- iterable_contains_unrelated_type
- list_remove_unrelated_type
- unrelated_type_equality_checks
- valid_regexps
It shows me No issues found!.
any progress?
how to solve this problem, I got the same issue as above.
I think we know understand what is happening here: the pub site used a different SDK version to analyze the source when analyzing the Flutter packages. There is an easy fix for that, but it may not be deployed today. Please be patient, the package's health score will be back to normal once we patch the issue and deploy a new version. I believe it should happen on Monday at the latest.
We are deploying a fix, with any luck this will be resolved in a few hours.
Thank you!
Looks like it has been fixed. Thank you!
Most helpful comment
I think we know understand what is happening here: the pub site used a different SDK version to analyze the source when analyzing the Flutter packages. There is an easy fix for that, but it may not be deployed today. Please be patient, the package's health score will be back to normal once we patch the issue and deploy a new version. I believe it should happen on Monday at the latest.