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

[Go] test picoschema with yaml test cases #528

Merged
merged 2 commits into from
Jul 4, 2024
Merged

[Go] test picoschema with yaml test cases #528

merged 2 commits into from
Jul 4, 2024

Conversation

jba
Copy link
Contributor

@jba jba commented Jul 3, 2024

Use the yaml file of test cases to test the Go picoschema implementation.

This uncovered a few problems. Some new features were implemented in
JS but not in Go; they are implemented here.

More seriously, it was discovered that the JSON schema package we
are using, github.com/invopop/jsonschema, does not support
arrays for the "type" field, and probably never will (see
invopop/jsonschema#134). Tests that
require that are skipped.

Use the yaml file of test cases to test the Go picoschema implementation.

This uncovered a few problems. Some new features were implemented in
JS but not in Go; they are implemented here.

More seriously, it was discovered that the JSON schema package we
are using, github.com/invopop/jsonschema, does not support
arrays for the "type" field, and probably never will (see
invopop/jsonschema#134). Tests that
require that are skipped.
@jba jba requested review from pavelgj, mbleigh and ianlancetaylor July 3, 2024 13:53
Copy link
Contributor

@ianlancetaylor ianlancetaylor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

@jba jba merged commit 6276db4 into main Jul 4, 2024
5 checks passed
@jba jba deleted the jba/picotest-go branch July 4, 2024 10:19
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

Successfully merging this pull request may close these issues.

2 participants