We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Sergio,
first thank you for all your contributions to the Remix community.
There are 2 places where JSON schema validation is too strict when using this with AWS cognito:
There is no "scope" in the token set so the TokenSetValueSchema validation fails.
TokenSetValueSchema
Suggestion: make it optional
The "email_verified" value is returned as a string ("true" or "false").
"true"
"false"
Suggestion: allow "true" and "false" literals for booleans with coercion
z.coerce.boolean()
It would be great if you could consider applying those changes, I can also contribute a PR.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi Sergio,
first thank you for all your contributions to the Remix community.
There are 2 places where JSON schema validation is too strict when using this with AWS cognito:
Token set "scope"
There is no "scope" in the token set so the
TokenSetValueSchema
validation fails.Suggestion: make it optional
User info schema "email_verified"
The "email_verified" value is returned as a string (
"true"
or"false"
).Suggestion: allow "true" and "false" literals for booleans with coercion
It would be great if you could consider applying those changes, I can also contribute a PR.
The text was updated successfully, but these errors were encountered: