You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When working with multiple frontends (e.g. various projects implemented in ReactJS) It would be super that the files of the queries, mutations and subscriptions could be downloaded in some way in these new frontends, brought from the main backend, and saved at an specific folder something similar when running the following command:
amplify codegen statements
It saves the queries, mutations and subscriptions and schema.json at the following default location /src/graphql/*.js
Describe the solution you'd like
Something similar to the following:
Describe alternatives you've considered
Pull the backend schema definition from cloud, and generate the schema, queries, mutations and subscriptions and save it at the default location /src/graphql/*.js
Additional context
Thanks in advance Paco
The text was updated successfully, but these errors were encountered:
kaustavghosh06
changed the title
amplify codegen statements from other frontends with a multi frontend environment setup
codegen on pull: amplify codegen statements from other frontends with a multi frontend environment setup
Jan 29, 2021
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Is your feature request related to a problem? Please describe.
When working with multiple frontends (e.g. various projects implemented in ReactJS) It would be super that the files of the queries, mutations and subscriptions could be downloaded in some way in these new frontends, brought from the main backend, and saved at an specific folder something similar when running the following command:
It saves the queries, mutations and subscriptions and schema.json at the following default location /src/graphql/*.js
Describe the solution you'd like
Something similar to the following:
Describe alternatives you've considered
Pull the backend schema definition from cloud, and generate the schema, queries, mutations and subscriptions and save it at the default location /src/graphql/*.js
Additional context
Thanks in advance
Paco
The text was updated successfully, but these errors were encountered: