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

codegen on pull: amplify codegen statements from other frontends with a multi frontend environment setup #224

Closed
fkoner opened this issue Sep 4, 2020 · 6 comments
Labels
amplify-codegen Issues on amplify-codegen feature-request New feature or request

Comments

@fkoner
Copy link

fkoner commented Sep 4, 2020

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:

amplify codegen statements --appId xxxxxxxxxxxxxx --envName itRocks

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

@akshbhu
Copy link
Contributor

akshbhu commented Sep 4, 2020

I have added this to our backlog for prioritization, once this is prioritized we will work on this. Feel free to 👍 so this gets more visibility

@fkoner
Copy link
Author

fkoner commented Sep 4, 2020

Thanks @akshbhu !!!!

@kaustavghosh06 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
@zirkelc
Copy link

zirkelc commented May 5, 2021

Any updates on this?

@levelingup
Copy link

@chriszirkel looks like they have that in the docs: https://docs.amplify.aws/cli/graphql-transformer/codegen#amplify-configure-codegen

@edwardfoyle edwardfoyle transferred this issue from aws-amplify/amplify-cli Aug 16, 2021
@phani-srikar phani-srikar added feature-request New feature or request amplify-codegen Issues on amplify-codegen labels Mar 29, 2022
@dpilch
Copy link
Member

dpilch commented Apr 4, 2024

This is now possible with:

amplify codegen add --apiId <appsync-api-id> --region <appsync-api-region>
amplify codegen

@dpilch dpilch closed this as completed Apr 4, 2024
Copy link

github-actions bot commented Apr 4, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amplify-codegen Issues on amplify-codegen feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants