feat: Expand flame_lint to respect required pub.dev checks #3139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Expand flame_lint to respect required pub.dev checks.
We are currently losing pub points due to lint violations:
Turns out
flame_lint
does not respect lints/core which is being enforced now by pub.This adds that as a dependency on
flame_lint
, updatesflutter_lint
for the packages that use that, and fix all existing violations (luckily very few).This change will ensure that us and everyone else who uses
flame_lint
get all the points they deserve on pub. We can consider expanding tolints/recommended
in the future, but that is definitely not a requirement at this stage (and a much bigger change).Checklist
docs
and added dartdoc comments with///
.examples
ordocs
.Breaking Change?