default log level #2
Open
Conversation
This file contains hidden or 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
This configuration values can be saved using: 1. Default values inserted by developer priority 0 2. Configuration file priority 1 3. Passed as command line arguments priority 2 Values with greater priority will overwrite values with less priority. Default value is overwritten by value in configuration file which is overwritten by value passed on command line. If no value was provided in configuration file or on command line then the default value will be used.
Some times we need to group configuration keys, for example to separate client configuration from server configuration and use the same conf file for both situations. All conf key that are at the beginning of the file and aren't under some section then this keys are in automatic inserted under default section.
…here is CR and LF at the same time. This difference cause an error when parsing config file on windows OS.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This configuration values can be saved using:
1. Default values inserted by developer priority 0
2. Configuration file priority 1
3. Passed as command line arguments priority 2
Values with greater priority will overwrite values with less
priority.
Default value is overwritten by value in configuration file which
is overwritten by value passed on command line.
If no value was provided in configuration file or on command line
then the default value will be used.
Why this modification?
Imagine you define loglevel flag with value like "ERROR" ... when all flags will parsed, doesn't matter if you have passed a loglevel on command line, this variable will not be empty. In this situation, how to check if I need to overwrite the loglevel value defined in configuration file (which can be equal to "DEBUG")?
or maybe we don't need to think about putt the loglevel in configuration file?