Add note about "Switch Build Server" in Metals. #1594
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Now that scalameta/metals#3308 is merged Metals can actually detect (based on mill version) if the current workspace can use Mill as a BSP server even if there is no
.bsp/mill-bsp.jsoncreated yet. If the users selects this, it will automatically create the.bsp/mill-bsp.jsonfile and then connect to mill. This pr just clarifies this in the docs and mentions the "Switch Build Server" command they'll need to use.Just to show an example, you can see here there is no bsp entry, but it's still shown as an option: