Recognize root of Enso repository as VSCode project #6942
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
JaroslavTulach
added
the
CI: No changelog needed
JaroslavTulach
force-pushed
the
wip/jtulach/ProjectForWholeEnsoRepo
branch
from
f71f134 to
ca4bb18
Compare
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.
Pull Request Description
Automatically recognize all Enso engine projects and open them in VSCode.
Important Notes
When one opens root of Enso repository in VSCode (after engine code is compiled with
sbt build) as workspace, then the project is recognized as Enso engine project:it brings in all the dependent projects, so one should automatically get:
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Java,