Allow per-folder configuration in multi-root workspaces #110
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.
This PR modifies the
scopeof several configuration settings offered by the extension. The goal of the changes is to allow settings to be modified on a per-project basis while operating in a multi-root workspace.Relevant documentation can be found under the scope heading in the Configuration schema section here.
The following checklist marks the configuration settings I've manually tested to ensure they are respected at the folder level: (Edit: all set.)
dialyzerEnableddialyzerWarnOptsdialyzerFormatmixEnvprojectDirfetchDepssuggestSpecsAs always, there may be unforeseen consequences to using the settings at this scope. Happy to help diagnose. 🙂
Addresses #58.