We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The readme for 3.0.0 states:
Precedence order When merging configuration values from different sources, Convict follows precedence rules. The order, from lowest to highest, is: Default value File (config.loadFile()) Environment variables Command line arguments Set and load calls (config.set() and config.load())
Precedence order
When merging configuration values from different sources, Convict follows precedence rules. The order, from lowest to highest, is:
Default value File (config.loadFile()) Environment variables Command line arguments Set and load calls (config.set() and config.load())
But as per the code and the conversation in issue #50 config.load appears to be at the precedence level of config.loadFile, not config.set.
The text was updated successfully, but these errors were encountered:
Similar/Duplicate : #211
Sorry, something went wrong.
Update Precendence order according implementation (#314)
946ead8
Fixes #211 and #208
9710356
node-blueconfig
Successfully merging a pull request may close this issue.
The readme for 3.0.0 states:
But as per the code and the conversation in issue #50 config.load appears to be at the precedence level of config.loadFile, not config.set.
The text was updated successfully, but these errors were encountered: