-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
JSONPath is an RFC now #2773
Comments
This is potentially dependent on JSONPath-plus having support for RFC 9535 (JSONPath-Plus/JSONPath#205) or changing the implementation of spectral to use another library. |
On 2025-02-04 16:47, Nauman wrote:
This is potentially dependent on JSONPath-plus having support for RFC 9535 (JSONPath-Plus/JSONPath#205 <JSONPath-Plus/JSONPath#205>) or changing the implementation of spectral to use another library.
Good point, I was naively assuming that JSONPath-plus is an implementation of RFC 9535 but it is not. My apologies for the confusion.
I am updating my PR to state that even though Spectral supports JSONPath, it is not the language that's standardized in the RFC of the same name.
|
Some interesting context about the slightly confusing history and evolution of the specification and implementations: P0lip/nimma#10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Documentation should be updated regarding JSONPath status. It is RFC 9535 now.
The text was updated successfully, but these errors were encountered: