Adding inputs (i.e. options incl. value) #1091
Merged
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.
Hello,
with this PR I would like to add the command line option
-I / --input
to specify options incl. a value, eg.--input 'checkxy:key:value'
This would for example allow to specify the path to external controlled vocabularies like MIP/CMOR tables for CORDEX, CMIP, etc. If there is a simpler way to achieve this, I would be happy to learn about it :)
The argument parser for
input
works similar to the one already present foroption
.I added the
inputs
as parameter to CheckSuite, ComplianceChecker and BaseCheck, similar tooptions
, with the defaultNone
. So I hope it does not interfere/conflict with anycompliance-checker
functionalities or existing plugins and simply serve as a means to supply options with values for specific checks.Kind regards,
Martin