You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certainly! Here's a revised version of the text, keeping the bullet points structure:
FVM now performs various checks for Dart SDK project constraints and dependencies to provide more informative feedback to the user. However, we have some suggestions to make this process even better.
It would be extremely helpful if FVM could install Flutter SDK based on a Dart SDK constraint. For example, running fvm use 2.14 --dart would install the latest version of Flutter that supports this version of Dart.
Also it would be great if FVM could easily run commands on the lowest and highest SDK constraint of pubspec. As a package creator, this is crucial for checking for deprecations or issues with the constraints.
When calling fvm dart ... if no version is configured in the project, and when falling back to PATH, it should fall back to Dart SDK configured in the Flutter SDK, and not the Dart SDK configured within the path
Certainly! Here's a revised version of the text, keeping the bullet points structure:
FVM now performs various checks for Dart SDK project constraints and dependencies to provide more informative feedback to the user. However, we have some suggestions to make this process even better.
fvm use 2.14 --dart
would install the latest version of Flutter that supports this version of Dart.fvm dart ...
if no version is configured in the project, and when falling back to PATH, it should fall back to Dart SDK configured in the Flutter SDK, and not the Dart SDK configured within the pathDiscussed in #532
The text was updated successfully, but these errors were encountered: