Look for validation files in custom paths #138
Merged
Conversation
This file contains 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
ncerutti
changed the title
Merged
benhayes21
approved these changes
Sep 19, 2024
sambles
pushed a commit
that referenced
this pull request
Sep 19, 2024
* add optional folders to validator paths * capture specific errors in validation, comments * pep * pep * remove lark version pin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Validation files in custom paths
When a custom path is passed in the configuration file, validation files in that folder will be found and used.
Validation files have to be provided in the appropriate format and filename. Failed validations will no longer interrupt the conversion, but will provide a warning message.
Solves #139.