fix: Correctly handle default configuration when user dirs do not exist #222
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.
We assumed that the user configuration directory hierarchy always exists, but with a completely fresh installation, it does not.
Consequently, populating the default configuration silently failed and the environment is broken.
To resolve this issue, we now check to see if the directory the configuration file lives in exists, and we create it if it does not.
Additionally, we now support populating a full set of default configuration in case multiple files and folders are required for initial configuration.