Feature (POC): Add default account overrides #227
Draft
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.
Description and Context
In this PR, I've created a small proof of concept for how we can implement default account overrides in the new configuration file with minimal code changes. For full details and proposals for future work, please see this Canvas.
One bug that @brandenrodgers and I discussed yesterday: Currently, I'm overriding the default account for a specific directory and its subdirectories. I think there's an edge case, where if a customer sets overrides for
~/projects/tmpand~/projects/tmp/sampleFolder, I'll need to make sure that files and folders within thesampleFoldersubdirectory respect the closest override (I hope that makes sense).TODO
Who to Notify
@brandenrodgers @camden11 @joe-yeager