-
Notifications
You must be signed in to change notification settings - Fork 23
Implement I-Regexp #66
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
Comments
As of 2024/09, I'm starting to take a run at this. If we get a substantial chunk of I-Regexp working, some of the other pattern upgrades can be re-implemented as regexes. Am going to do this incrementally, pulling in features one at a time, but have to have a full parser because we should reject regexes that use unimplemented features. |
timbray
added a commit
that referenced
this issue
Jan 6, 2025
partially addresses #66 Signed-off-by: Tim Bray <tbray@textuality.com>
timbray
added a commit
that referenced
this issue
Jan 31, 2025
partially address #66 Signed-off-by: Tim Bray <tbray@textuality.com>
BTW I-Regexp is now RFC 9485. |
timbray
added a commit
that referenced
this issue
Feb 4, 2025
partially address #66 Signed-off-by: Tim Bray <tbray@textuality.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The IETF JSONPath WG is building a minimal-ish regular expression specification called I-Regexp designed to be interoperable across a wide variety of regex implementations. See https://www.ietf.org/id/draft-ietf-jsonpath-iregexp-00.html
A full or even subset implementation of I-Regexp would be a valuable addition to Quamina.
The text was updated successfully, but these errors were encountered: