-
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
handle unmatched types in permission builder #3712
handle unmatched types in permission builder #3712
Conversation
Deploy preview for hasura-docs ready! Built with commit 60ec65e |
Review app for commit 6db6fe7 deployed to Heroku: https://hge-ci-pull-3712.herokuapp.com |
'dateTime', | ||
'numeric', | ||
'uuid', | ||
'user_defined', |
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.
Isn't this list the same for every operator? Would it make sense to extract it to the variable, so that another changes would be done just in the one place?
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.
It does seem like there can be a better way to represent this info. Will take a stab at it and request a review
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.
@beerose Made changes to avoid repetition in the future as well. This was a good catch. Thanks.
Review app for commit ad5f590 deployed to Heroku: https://hge-ci-pull-3712.herokuapp.com |
…k/graphql-engine into console-permissions-unknown-types
Review app for commit 60ec65e deployed to Heroku: https://hge-ci-pull-3712.herokuapp.com |
Review app https://hge-ci-pull-3712.herokuapp.com is deleted |
Description
In permission builder, for columns with types not present in the mainitained list, a default set of operators will always get shown
Affected components
Related Issues
#3603
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
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