-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Editor: Semantic versioning smarts for pubspec editing #19389
Comments
This comment was originally written by @seaneagan and issue #18555 is about publishing pub's semver code for this |
Added Area-Editor, Triaged labels. |
Set owner to @keertip. |
This comment was originally written by @seaneagan Ideally, this functionality would be built-in to pub (issue #18911), and the editor would just call pub when the various buttons are clicked. But adding it to the editor might be quicker than adding it to pub, so that'd be nice to have in the meantime, and might drive some feedback to use in issue #18911. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
Agreed, something like this might be better for an external utility. Added NotPlanned label. |
Added this to the 1.6 milestone. |
This issue was originally filed by @seaneagan
The editor already has a GUI for pubspec editing with a button to add a new dependency. It currently defaults the version constraint to "any". It would awesome if instead it looked at the latest version, and suggested a version range that guarantees I won't be subject to any breaking changes, so long as the dependency's author adheres to semantic versioning. Some examples:
0.0.5 -> '>=0.0.5 < 0.1.0'
0.4.1 -> '>=0.4.1 < 0.5.0'
1.2.3 -> '>=1.2.3 < 2.0.0'
Whenever you
pub publish
withany
constraints from the editor, it already warns and makes such suggestions, so whatever code is used there could be reused.It might also be nice to have a button to update either a single dependency or all dependencies to the latest version, which would use similar version constraints as above.
The text was updated successfully, but these errors were encountered: