-
Notifications
You must be signed in to change notification settings - Fork 29.7k
[tool] Remove all usages of the deprecated usage package #151518
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
Conversation
packages/flutter_tools/lib/src/reporting/custom_dimensions.dart
Outdated
Show resolved
Hide resolved
f2b493b to
7427786
Compare
9d282f0 to
ad44d04
Compare
ad44d04 to
0afffb4
Compare
chingjun
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.
Internally we are still depending on the code removed in this PR for analytics. We need to migrate it to use the new Analytics class before removing package:usage here.
This PR shouldn't remove any APIs that g3 needs, it should only remove the usage of those APIs within the tool itself. |
The |
Oh. So these calls, which are effectively no-ops for open-source flutter since GA3 is offline, are not no-ops for g3 flutter? |
Could you please link these? I am not sure if you are referring to call sites or definitions here. |
|
One example I see is that g3 depends on overriding |
|
Closing since I don't have the bandwidth to continue work on this. I will update the parent issue. |
| environment: <String, String>{ | ||
| 'JAVA_HOME': javaHome, | ||
| 'FLUTTER_ANALYTICS_LOG_FILE': analyticsOutputFile.path, | ||
| 'FLUTTER_SUPPRESS_ANALYTICS': '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 doubt FLUTTER_SUPPRESS_ANALYTICS is actually needed since we have bot detection elsewhere, but I would rather delete all of these in a separate PR.
Split-off from #151518. Helps #150575 <details> <summary> Pre-launch checklist </summary> - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. </details> <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
|
For archeologists: this was before the monorepo merge and before we got the OK to delete g3 dependence on package:usage. This entire PR, the review, and my understanding of things went stale by the time I was ready to pick this up again, so this was since replaced by smaller PRs. See parent tracking issue. |
Helps #150575.
Also fixes #150665.
Also fixes #150663.
Also fixes #151560.
This is a recreation of #150667. I was originally going to split this up into smaller PRs, but this has proven very time-consuming and is prone to accidentally overwriting changes that land in between the smaller PRs.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.