-
-
Notifications
You must be signed in to change notification settings - Fork 313
Regex editorial improvements, and permit "." #1470
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
Conversation
Consistently "quote" examples. Split complemented simple and range class examples. Improve "(" .. ")" grouping example.
We've discussed this before, and I think it may be worth bringing it up again. IETF has now published https://datatracker.ietf.org/doc/rfc9485/ to support interoperable regex in JSON Path. It may be wise to reconsider this in place of ECMA. Doing so would mean being able to remove all of these restrictions. |
@gregsdennis I feel like I'm inclined to agree with this person's opinion that iregexp is not a good fit for JSON Schema - though I have not kept up with any changes since 2022 that may have changed that situation. |
Yeah, I hear you. But finding interoperable regex support has been a thorn in our side for a long time. It really has no bearing on this PR, though. |
I've added 3 commits addressing various review feedback above. |
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.
This looks fine to me.
Add "." to the permitted simple atoms, for issue #1469.
Consistently format the regex examples.