Skip to content
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

Sublime Semver Support #1362

Closed
Thom1729 opened this issue May 23, 2018 · 2 comments
Closed

Sublime Semver Support #1362

Thom1729 opened this issue May 23, 2018 · 2 comments

Comments

@Thom1729
Copy link

It would be easier for package authors to declare sublime version support using semantic version numbers instead of build numbers, such as ">=3.0" rather than ">=3000". I think that this would significantly reduce the number of package submissions that declare the wrong version (e.g. 3000 when the package includes a sublime-syntax). Developers targeting dev builds could still declare them.

@FichteFoll
Copy link
Collaborator

FichteFoll commented Jun 8, 2018

The downside is that we'd require a lookup table for all previous and future release versions to translate them back to build numbers because you don't get the semantic number from the API.

I do agree that the people having to specify >=3092 is annoying, however. The same applies to .sublime-color-scheme as well, which we don't have a check for yet.

@deathaxe
Copy link
Collaborator

With ST4 dropping versioning, that change doesn't make sense anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants