Strict spec validation #127
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
support error reporting when a configuration file contains entries that are not defined by the validator definitions.
|
@jhermann I hope you don't mind the ping, but I noticed you active here last week and was hoping I could get a response to my pull requests and open issues. It has been over a month since this was submitted, and I need to make a decision to continue with configobj, fork, or pursue an alternative. Thanks either way. |
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.
Implements a backwards compatible
strict_specvalidation mode:If
strict_specisTrue(Falseis default) then instead ofignoring entries undefined by the configspec, unrecognized entries will
fail validation and be inserted into the return dictionary with an
informational
ValidateError.Closes issue #125.