Update permission.rst for check constraint API #3883
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for hasura-docs ready! Built with commit 2f6a7c6 |
marionschleifer
suggested changes
Feb 24, 2020
Contributor
marionschleifer
left a comment
There was a problem hiding this comment.
Just some small changes, otherwise all good 🙂
docs/graphql/manual/api-reference/schema-metadata-api/permission.rst
Outdated
Show resolved
Hide resolved
docs/graphql/manual/api-reference/schema-metadata-api/permission.rst
Outdated
Show resolved
Hide resolved
docs/graphql/manual/api-reference/schema-metadata-api/permission.rst
Outdated
Show resolved
Hide resolved
Co-Authored-By: Marion Schleifer <marion@hasura.io>
marionschleifer
approved these changes
Mar 16, 2020
Contributor
|
Review app https://hge-ci-pull-3883.herokuapp.com is deleted |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I missed this in my PR for #384. I noticed the existing docs were incorrect, so I fixed a few mistakes too. Namely:
checkwhich didn't exist previously, presumably copied from the insert API docs.setexample didn't really make sense since you wouldn't want to set the article ID to a user ID value.Affected components
Catalog upgrade
Does this PR change Hasura Catalog version?
Does this PR add a new Metadata feature?
GraphQL
Breaking changes