Refactored config to not use viper singleton instance #1027
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.
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
Refactors how the configs are initialized and fixes
config init
.Configs are managed using the
viper
package singleton,config init
command reads from existing settings when initializing a new config file.Configs are not managed anymore with the
viper
package singleton but using a global variable internal to theconfiguration
package of thearduino-cli
.The
config init
command now initializes new config files using the default values without reading from existing files.Yes.
None.
See how to contribute