Add support for glob alike pattern matching #83
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.
This pull-request adds support for similar behavior for
*and**of glob patterns. This is a breaking change since previously*meant to match anything afterwards.Besides being more intuitive for developers, glob matching allows for a common use-case of whitelisting properties of a given key, regardless of their depth. For example
**.error.codewill whitelisterror.codeat any tree level. Previously, we would had to repeat both**.error.codeanderror.codeto have the same behavior, or to use*error.codewhich will also whitelist anything that isn't namederrorexactly.Also revamped README and tests.