-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed as not planned
Closed as not planned
Copy link
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Flutterc: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.
Description
Forked from #143312.
This is a catch-all issue/wishlist for having better tooling or process for minimizing and reducing usages of deprecated stuff1.
Anyone is welcome to add their thoughts, but:
- Please be respectful.
- These are for tools and process for Flutter contributors, not users, i.e. for the Flutter framework itself.
- When possible, explain the problem you're trying to solve before suggesting a solution.
It's also not clear who or when this work will get done, but we can discuss priorities as a team.
I'll start with a few seeded ideas:
1-time allow-listing all existing deprecations and making future ones breaking
Imagine the following API:
// package:foo/foo.dart
final class Foo {
void bar() {}
}In a roll, the following happens:
// package:foo/foo.dart
final class Foo {
+ @Deprecated('Use baz() instead')
void bar() {}
+ void baz() {}
}... a bot could automatically add:
+ // ignore: deprecated_member_use
foo.bar();... to all existing call-sites, and then make that symbol breaking for future usages.
Create a dashboard that tracks deprecated member usages
... potentially with WoW or MoM changes.
| Import | Symbol | Current | Last 30 Days |
|---|---|---|---|
package:foo/foo.dart |
Foo.bar |
3 | +1 (33%) |
Footnotes
-
I'd say code, but perhaps you could extend this to "using Groovy instead of Kotlin for Gradle", etc. ↩
goderbauer, jacob314 and polina-c
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Flutterc: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.