Add JSON schema based BOM validator. #135
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
|
bump |
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.
BOM decoder is not providing possibility to validate the values of the BOM. Nevertheless boundaries and expectations are set for some of them and it seemed necessary to have a possibility of validating these values.
Current proposal include separated validator (not a part of decoder) that operates on decoded json (BOM struct) scanning corresponding JSON schemas for enum/pattern schema definitions for the non-empty BOM fields. BOM fields are validated to either match any ENUM option or RegEx pattern. This way there is no need to create separate validation definitions.