Make flutter analyze --suggestion provide suggested versions in all error messages
- Dominant language
- Dart
- Stars
- 179k
- Forks
- 31.1k
- PR merge metrics
- PR metrics pending
Description
`flutter analyze --suggestions` can tell users when their versions are incompatible but not what the right version is.
Multiple users have told me as an example that https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin is too many words and they will continue to be frustrated rather than read the documenation.
The fallback solution seems to be to run flutter create then diff the gradle files. This happens even with full time flutter contributors.
Adding to this confusion is that the newest of all versions fail the compatibility check even though the builds appear to work even at scale. Kotlin full support seems like it is limited to a couple of AGP versions older than the most recent which we might warn on but not suggest downgrading.
Contributor guide
Research direction
Start with the flutter analyze --suggestions output and the Gradle files produced by flutter create, which the issue identifies as the relevant entry points. Define and verify how supported versions should be suggested for each compatibility error, including when to warn about newer versions rather than recommend downgrading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, kotlin
- Domain
- build-system, cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100