-
Notifications
You must be signed in to change notification settings - Fork 29.8k
delete almost all remaining references to package:usage #162658
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
delete almost all remaining references to package:usage #162658
Conversation
| @override | ||
| bool get reportNullSafety => true; | ||
|
|
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.
I don't see any package:unified_analytics event for reporting null-safety (or rather the lack of it). Disabling null-safety is not possible in the tool (outside of forks). I'm speculating that this information has no known use case and that this code should be deleted.
| void main() { | ||
| testWithoutContext('DoctorResultEvent sends usage event for each sub validator', () async { |
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.
These doctor tests are covered in doctor_test.dart
| globals.logger.fatalWarnings = boolArg(FlutterOptions.kFatalWarnings); | ||
| } | ||
| // Prints the welcome message if needed. | ||
| globals.flutterUsage.printWelcome(); |
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.
Isn't this still needed?
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.
We print a consent message upon exit
| globals.logger.printStatus(globals.analytics.getConsentMessage); |
Unless you are saying we should keep this until we actually remove the package completely
|
@andrewkolos do you have a couple of cycles to get this ready for landing? |
|
Sure do! I just need to stop forgetting about it |
bkonyi
left a comment
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.
The changes to remove package:usage reference still LGTM, but I think there's something wrong with the formatting changes.
| abstract class DotEnvRegex { | ||
| // Dot env multi-line block value regex | ||
| static final RegExp multiLineBlock = RegExp(r'^\s*([a-zA-Z_]+[a-zA-Z0-9_]*)\s*=\s*"""\s*(.*)$'); | ||
| static final RegExp multiLineBlock = RegExp( |
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.
I'm not sure these formatting changes are correct given what's currently at HEAD. Maybe the 100 character limit set in analysis_options.yaml isn't being respected properly?
|
This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold. For more guidance, visit Writing a golden file test for Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
@andrewkolos @bkonyi I'm guessing this isn't being worked on any more? Should we close it for now? |
Toward #150575. The idea of this PR is to get as close as possible to removing package:usage without actually deleting the dependency from the tool pubspec. That will be a separate PR since that has a decent chance of running into internal roll complications.
Pre-launch checklist
///).