update metadata when constraints on a table are altered (fix #240) #1229
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
Contributor
|
Review app for commit f282c8c deployed to Heroku: https://hge-ci-pull-1229.herokuapp.com |
Resolve Conflicts: server/src-lib/Hasura/RQL/Types/SchemaCache.hs
…raphql-engine into rakeshkky-issue-240-constraint
Contributor
|
Review app for commit 691ffe7 deployed to Heroku: https://hge-ci-pull-1229.herokuapp.com |
Member
|
closing in favor of #1287 |
Contributor
|
Review app https://hge-ci-pull-1229.herokuapp.com is deleted |
hasura-bot
pushed a commit
that referenced
this pull request
Oct 16, 2024
<!-- The PR description should answer 2 important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> The `example` JSON schema attribute can be specified multiple times enabling inclusion of multiple examples. The OpenDd metadata is auto-documented in hasura.io/docs using the json schema. Having multiple examples is quite helpful for our users. Inspired from the `schemars`'s `example` attribute behavior. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> - Use `#[darling(multiple)]` attr to allow the `example` attribute multiple times. - Add more examples for model predicates and permission. V3_GIT_ORIGIN_REV_ID: 7e9c31891afed5b96ec8a5bb7538062382ef4d27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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
What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
fix #240
Solution and Design
Reload table constraints whenever
run_sqlquery is made.Type
Checklist: