-
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 the nextjs postgres graphql sample app, close #7672 #9048
Conversation
Beep boop! 🤖 Hey @amit-ksh, thanks for your PR! One of my human friends will review this PR and get back to you as soon as possible. Stay awesome! 😎 |
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.
Everything looks good apart from the admin secret usage. Please make the relevant changes for that (ideally, remove the admin secret usage and don't have any authentication, make a public role with Unauthorized access).
78c9a5d
to
4921dae
Compare
GITHUB_PR_NUMBER: 9048 GITHUB_PR_URL: #9048 PR-URL: hasura/graphql-engine-mono#6159 Co-authored-by: Amit Kumar Sharma <91947037+amit-ksh@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> GitOrigin-RevId: 0565d8a00c944d72b46bc5ce0ff40fc3e8bfca51
Beep boop! 🤖 Awesome work @amit-ksh! Your changes were merged successfully. All of us at Hasura ❤️ what you did. Thanks again 🤗 |
Description
Rebuild the sample app using the latest version of NextJS and ApolloClient.
Changelog
Component : community
Product: community-edition
Short Changelog
Related Issues
#7672
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