Skip to content
New issue

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

Readme precedence lists load as being equivalent to set #208

Open
casba opened this issue Jun 6, 2017 · 1 comment · Fixed by A-312/node-blueconfig#1
Open

Readme precedence lists load as being equivalent to set #208

casba opened this issue Jun 6, 2017 · 1 comment · Fixed by A-312/node-blueconfig#1

Comments

@casba
Copy link

casba commented Jun 6, 2017

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())

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.

@A-312
Copy link
Contributor

A-312 commented Dec 7, 2019

Similar/Duplicate : #211

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants