Merged
Conversation
This file contains hidden or 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
1 participant
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.
The mise-vscode has an option
configureExtensionsAutomaticallywhich will automatically setup the paths to binaries for runtimes like deno, node, python, etc for anything configured in mise and used by vscode. This ends up writing absolute paths to thesettings.jsonwhich makes it hard to share settings with other folks. This is more a failing of vscode than of mise-vscode. To attempt to help with this issue,mise-vscodewill do automatic symlinking in.vscode/mise-toolsand configure local paths. As I unfortunately found out, vscode also doesn't path references they provide for extensions to consume so support of these features is dependent on an extension maintainer's willingness to add it. The deno team refused to add this support which ultimately makes it feel like a non-starter to me.Thankfully @swellaby implemented vscode-workspace-config-plus which gives some rudimentary ability to share config. It doesn't look like the extension is actively maintained, but its functional enough to achieve what I need from it.