-
Notifications
You must be signed in to change notification settings - Fork 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
Move top-level packages, and testing/*
, to pub workspaces
#53997
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
||
linter: | ||
rules: | ||
- public_member_api_docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the Flutter GPU analyzer failures, would it make sense to keep this old rules file until I'm able to migrate it to the new rules we've agreed on for Flutter Engine Dart files?
I am taking this back to a draft so I can land things more piece-meal, as I really don't understand the failures |
This pull request has been changed to a draft. The currently pending flutter-gold status will not be able to resolve until a new commit is pushed or the change is marked ready for review again. |
More incremental version of #53997.
Partial work towards flutter/flutter#147883.
This should be a no-op, that is, there are no changes to behavior or dependencies as part of this change.