Skip to content

Fixing the analyzer infos #733

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

Closed
4 tasks done
fischerscode opened this issue Apr 30, 2022 · 3 comments · Fixed by #810
Closed
4 tasks done

Fixing the analyzer infos #733

fischerscode opened this issue Apr 30, 2022 · 3 comments · Fixed by #810
Labels
type:feature New feature or improvement of existing feature

Comments

@fischerscode
Copy link
Contributor

New Issue Checklist

Issue Description

Currently the dart and the flutter package have many analyzer infos.
It's a good practice to fix them.

Some require breaking changes. Those should wait for the next major release.

Steps to reproduce

flutter analyze package/flutter
dart analyze package/dart

Actual Outcome

n/a

Expected Outcome

n/a

Environment

n/a

Logs

n/a

@parse-github-assistant
Copy link

parse-github-assistant bot commented Apr 30, 2022

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:ci CI related issue label Apr 30, 2022
@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed type:ci CI related issue labels Apr 30, 2022
@mbfakourii
Copy link
Member

mbfakourii commented Dec 20, 2022

It seems to be resolved in issue #757 and I am resolving the new warnings

@mtrezza
Copy link
Member

mtrezza commented Dec 21, 2022

Reopened for #810

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants