Skip to content

Add 2 tools to tooling data #1636

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add 2 tools to tooling data #1636

wants to merge 2 commits into from

Conversation

zx80
Copy link

@zx80 zx80 commented May 4, 2025

What kind of change does this PR introduce?

Add entries for:

  • JSON Schema Utils (analyze/lint, prettyprint, simplify, convert to model)
  • JSON Model (convert to schema)

Issue Number:

None

If relevant, did you update the documentation?

Not relevant.

Summary

Add new references to tools which process or generate schemas.

Does this PR introduce a breaking change?

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

Add descriptions for
- JSON Schema Utils (analyze/lint, prettyprint, simplify, convert to model)
- JSON Model (convert to schema)
@zx80 zx80 requested a review from a team as a code owner May 4, 2025 06:45
@Relequestual
Copy link
Member

Thanks for your work and for adding your work to the list!

I'm not sure about adding 'next' dialect to your list of supported dialects. It will change in the future.
I've asked others what they think about this. Will report back (or others may just come comment themselves.)

@zx80
Copy link
Author

zx80 commented May 11, 2025

I'm not sure about adding 'next' dialect to your list of supported dialects. It will change in the future. I've asked others what they think about this. Will report back (or others may just come comment themselves.)

Hello Ben,

The motivation for mentioning next is because the analysis tool attempts to guess schema version compatibility based on used keywords, and propertyDependencies triggers next because it is a new keyword for now which adds a concept somehow similar to OpenAPI discriminator extension. There is no problem to remove the mention anyway.

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