Skip to content
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

Dynamic Schema Generation #38

Merged
merged 13 commits into from
Sep 12, 2024
Merged

Dynamic Schema Generation #38

merged 13 commits into from
Sep 12, 2024

Conversation

WyzaXX
Copy link
Collaborator

@WyzaXX WyzaXX commented Sep 9, 2024

  • Added dynamic schema generation per chain. Now the number of tables is significantly reduced in the graphql explorer.
  • Splitted the schemas into separate ones with the main one included. (This is used by the generateSchema.ts).
  • Made a script so that the deployment process is easy (deploy.sh).
  • Added a readme.md in the pallets folder describing why @ts-ignore is used.
  • Updated main readme.md

Additional Changes:

  • Extended db capacity moonbeam and moonriver in the manifests.

Notes:

  • generateSchema.ts is the main logic for dynamically generation the schema.graphql
  • deploy.sh is now used when deploying a chain into the cloud. sqd deploy is still used, just with some prerequisites before that.
  • After deploying all changes made by the script are removed to not mess with local development.

All chains need to be redeployed to remove the unused tables.

@WyzaXX WyzaXX self-assigned this Sep 9, 2024
@nistanimirov nistanimirov added this to the Improvements milestone Sep 9, 2024
@WyzaXX WyzaXX merged commit c5c1931 into main Sep 12, 2024
2 checks passed
@nistanimirov nistanimirov linked an issue Sep 13, 2024 that may be closed by this pull request
@WyzaXX WyzaXX deleted the feat/dynamic-schema-generation branch September 27, 2024 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

QoL improvements and refactoring
3 participants