build(schema): Add explicit escape to opening bracket matcher in jp/jsonpath regex #3719
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
|
Rebase to develop |
|
Whoops, sorry about that! Base changed to develop. |
Ash258
previously approved these changes
Nov 8, 2019
21 tasks
rashil2000
previously approved these changes
Jan 8, 2022
niheaven
approved these changes
Jan 8, 2022
niheaven
changed the title
se35710
pushed a commit
to se35710/scoop
that referenced
this pull request
Mar 8, 2022
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.
This PR adds an explicit escape to the opening bracket matcher for the
"jp"|"jsonpath"properties in the JSON schema.This resolves the following issue with manifest validation in IntelliJ IDEA:
There were 4 instances of this pattern in the schema, so they were extracted to a sub-schema at
#/definitions/jsonPathPattern.