-
Notifications
You must be signed in to change notification settings - Fork 27
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
[@kadena/graph] Feat: Update prisma schema to follow naming convention #998
Conversation
… result is fetched
…s and subscriptions accordingly
…at/prisma-schema-naming-convention
🦋 Changeset detectedLatest commit: 01066a9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 5 Ignored Deployments
|
…ema-naming-convention
…aph/event-parameters-formatting
…ers-formatting [@kadena/graph] , [@kadena/graph-client] Fix - Eventparameters fix and small adjustments
#998) * removed event parameters and added paramtext; adjusted the client pages accordingly * fix fetching of events and eventpage * change while statement on block so that subscription stops even if no result is fetched * add empty changeset * lint fix * removed commentary * fix lint * applied naming convention on prisma fields and changed graphql queries and subscriptions accordingly * add empty changeset * apply naming convention to powhash field * change graphql field accordingly * changes in client to accomodate graphql schema changes * changed paramText to new naming convention in client
Updated prisma schema fields to follow naming convention
camelCase
and changed necessary files accordingly