-
Notifications
You must be signed in to change notification settings - Fork 31
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
LSP-* versions should be based on the min/max version of LSP #97
Closed
Closed
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c94763a
fix: LSP-* versions should be based on the min/max version of LSP
predragnikolic f6f7596
fix the rest of the versions
predragnikolic 074d364
revert Julia because it uses sublime_plugin.ListInputHandler, and Cop…
predragnikolic 9560c10
revert volar because it uses CLEAR_TO_RIGHT(4100) and command_url(4075)
predragnikolic 9c26ac7
revert lsp-yaml because it uses find_syntax_for_file(4081)
predragnikolic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not possible to change to 4070. I put this on purpose to 4095 because LSP-julia uses
sublime.ListInputItem
which was introduced with ST 4095.The 4070 restriction for the main LSP package is mostly meaningless anyway, because I'm almost sure it uses various things from the ST API that were introduced after build 4070. Personally I also don't like the
4070-
prefix for the version tags (purely for aesthetic reasons). iirc it was introduced to make it possible to add new release prefixes with increased build numbers whenever new functionality from the ST API gets used in LSP. But apparently this didn't happen in the past and also nobody really cares about it, so I guess it can just stay like this (4070) forever and in the case of any issue reports get filed in the future for the use of API incompatible with older ST builds, we could just fix those gradually withif ST_VERSION > XXXX
checks in the code, if possible.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing that out.
I went through the LSP-* packages again
and checked if other packages use
sublime.*
apis introduced in later versions of ST and reverted the versions.