Skip to content
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

Is it possible to provide other language implementation? #74

Open
He-Pin opened this issue May 7, 2024 · 8 comments
Open

Is it possible to provide other language implementation? #74

He-Pin opened this issue May 7, 2024 · 8 comments

Comments

@He-Pin
Copy link

He-Pin commented May 7, 2024

Motivation:
I'm using Java, is it possible to provide a suite for Java, thanks.

@He-Pin
Copy link
Author

He-Pin commented May 7, 2024

I'm using dynamicTest of Junit5, it's works, thanks.

@gregsdennis
Copy link
Collaborator

This suite is defined in plain JSON, which should be readable in just about every language. You'll have to build your own test runner though.

My implementation is .Net, so I had to build a runner that reads the cts.json file and processes all of the test cases. You can see the code for it here.

@hiltontj
Copy link

hiltontj commented May 7, 2024

I also did something similar to @gregsdennis in serde_json_path (Rust), see here.

@f3ath
Copy link
Collaborator

f3ath commented May 8, 2024

Same in Dart: https://github.com/f3ath/jessie/blob/master/test/helper.dart

@aljopainter
Copy link

It's nice to see the different implementations for the new proposed standard. I'm wondering if there is a good place to put a list of implementations for RFC9535.

@f3ath
Copy link
Collaborator

f3ath commented May 20, 2024

I'm not aware of one, but this table would be an appropriate place to have such a list https://cburgmer.github.io/json-path-comparison/

@aljopainter
Copy link

I'll see if I can motivate adding a section for implementations that are supposed to be conformant with the new proposed standard.

@gregsdennis
Copy link
Collaborator

I already have cburgmer/json-path-comparison#130, but it seems that work on that repo has waned since the spec was released. I think it was intended as just a tool to inform the spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants