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

Add accept latest-stable and latest-snapshot as server versions #97

Merged
merged 4 commits into from
Sep 16, 2022

Conversation

ayoub-benali
Copy link
Collaborator

Fix #61

I am not sure if this exactly the same behavior as the vscode and vim plugins.
@tgodzik are the other clients released now with latest-stable a default server version ?

cc @ninth-dev

@tgodzik
Copy link

tgodzik commented Sep 16, 2022

Fix #61

I am not sure if this exactly the same behavior as the vscode and vim plugins. @tgodzik are the other clients released now with latest-stable a default server version ?

cc @ninth-dev

For VS Code we have a prerelease version, which tries to update the snapshot to the newest one, but the main releases are on stable versions. I think if the user knows what they are doing this should be fine.

@ayoub-benali
Copy link
Collaborator Author

Ok then I will change the default version here: https://github.com/scalameta/metals-sublime/blob/master/LSP-metals.sublime-settings#L3 to be latest-stable by default to avoid having to make a new release of this plugin each time metals makes a new stable release

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

Successfully merging this pull request may close these issues.

Add setting to use latest snapshot or latest stable automatically
2 participants