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

Displaying why one schema isn't a subset of another #25

Open
crdoconnor opened this issue May 22, 2024 · 1 comment
Open

Displaying why one schema isn't a subset of another #25

crdoconnor opened this issue May 22, 2024 · 1 comment

Comments

@crdoconnor
Copy link

Is it straightforward to provide a list of fields which invalidate one schema being a subset of another? - i.e. debugging information

Currently if you use this to validate schema compatibility, it does give a yes/no answer but it doesn't provide any context. In large schemas, you would have to manually dig around to figure out what broke.

This may be a large chunk of work and I'd understand if you didn't want to do it. I'm thinking of forking and and providing this functionality in a separate project along with #24, but I thought I'd drop a note here first just in case these were features that you were considering.

@hirzel
Copy link
Member

hirzel commented May 22, 2024

If you want to consider contributing better error reporting, we would welcome that!

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

2 participants