-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Update Auth0 docs to note which token to update when using auth0-spa-js. #3367
Conversation
Beep boop! 🤖 Hey @nirvdrum, thanks for your PR! One of my human friends will review this PR and get back to you as soon as possible. Stay awesome! 😎 |
Deploy preview for hasura-docs ready! Built with commit 4afcbe7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. The sample apps actually use the older version of Auth0 right now. The code upgrade can happen in a different PR if necessary.
@rikinsk Pinging you to merge this. |
Beep boop! 🤖 Awesome work @nirvdrum! All of us at Hasura ❤️ what you did. Thanks again 🤗 |
Review app https://hge-ci-pull-3367.herokuapp.com is deleted |
Description
Depending on which Auth0 SDK you're using, the rules you use to add Hasura claims to the JWT need to be adjusted. This change clarifies the differences and provides code samples for them.
Affected components
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changed