Fixing regex handling in "patternProperties"
#188
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.
Changing
ObjectSchema
to representpatternProperties
as aMap<Regexp, Schema>
instead ofMap<Pattern, Schema>
This is a follow-up change of introducing
Regexp
andRegexpFactory
interfaces in1.9.0
.Keeping but deprecating existing accessor & builder methods of
ObjectSchema
which consume / return aPattern
, converting from/toRegexp
.In the end, changing
ObjectSchemaLoader
to instantiate aRegexp
instance using the configuredRegexpFactory
instead of attempting to use RE2J directly.Also bumping version number to 1.9.1, since it is going to be a quick bugfix release ASAP.