Skip to content
This repository has been archived by the owner on Oct 14, 2020. It is now read-only.

JSONPath comparison and standardisation #55

Open
glyn opened this issue Jun 10, 2020 · 2 comments
Open

JSONPath comparison and standardisation #55

glyn opened this issue Jun 10, 2020 · 2 comments

Comments

@glyn
Copy link

glyn commented Jun 10, 2020

@cburgmer's JSONPath comparison project is currently discussing some issues relating to a proposed implementation of JSONPath known as "Proposal A". May I encourage you to get involved if you are interested in influencing the direction or, indeed, if you want to make your own proposals.

Similarly, please join us in slack (invitation) for informal discussions on the comparison project and potential JSONPath standardisation.
@martinssipenko martinssipenko mentioned this issue Oct 14, 2020
Merged
@martinssipenko
Copy link
Contributor

This project is now marked as abandoned and suggests using softcreatr/jsonpath as a replacement. If you think this issue is still relevant please open a new ticket under the new project.

https://github.com/SoftCreatR/JSONPath

1 similar comment
@martinssipenko
Copy link
Contributor

This project is now marked as abandoned and suggests using softcreatr/jsonpath as a replacement. If you think this issue is still relevant please open a new ticket under the new project.

https://github.com/SoftCreatR/JSONPath

@glyn glyn mentioned this issue Oct 14, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@glyn @martinssipenko