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

contentEncoding accepted values are not the same as jsonschema's spec #121

Open
dtheodor opened this issue Sep 8, 2024 · 1 comment
Open

Comments

@dtheodor
Copy link

dtheodor commented Sep 8, 2024

This library expects "base-64", "base-32" and so on. The jsonschema spec specifies "base64", "base32" etc.

@ghandic
Copy link
Owner

ghandic commented Sep 8, 2024

PR Welcome!

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