-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wildcard matching #397
Wildcard matching #397
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noted. Looks good to me!
Following the discussion in ScenarioMIP, I think we might want to have full regex capabilities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the feature is useful, but I would not use fnmatch based on earlier experience (see inline comment).
about regexp, maybe we can abuse regexp-notation (as a follow-up PR) like
- scen_a # direct match
- scen_* # wildcard match
- r’scen_[.]’ # regexp match
@@ -0,0 +1 @@ | |||
- scen_* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could make sense to start putting codelist-validation test data into an own subfolder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, bit of cleanup is a good idea for sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cleaned up the complete test data folder in #399. Once that PR is merged, I'll rebase this one and move this file.
Updated to using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
829a816
to
2cf4763
Compare
Closes #294.
While this PR is ready in principle (minus documentation), I'd see it as a basis for discussion if we actually want this feature.