[request?] amplify codegen does not reflect updated schema from local copy

[swyxio]

Is your feature request related to a problem? Please describe.

Problem 1: codegen doesnt codegen from local copy

when i update my local schema in /amplify/backend/api/MYAPI/schema.graphql and run amplify codegen, the generated code in src/graphql doesn't update at all.

we are not sure if this is a bug or working as intended. but it's clear that in order to update the generated code i have to amplify push.

Problem 2: CLI gives the impression that codegen is done before push

I have to amplify push before i can codegen the new model:

this causes a LONG wait time and completely breaks my flow, for information i already have on my machine.

I ran amplify push 40 minutes 1 hour ago and am still waiting for my updated graphql schema so i can continue working. this is not a sustainable workflow when i'm just changing one little field on my schema.

Repro steps

1. amplify add api
2. amplify codegen
3. change one field in the graphql schema
4. amplify codegen again
5. observe that nothing has changed in src/graphql

Describe the solution you'd like

i understand you do this in order to always codegen the right thing. but perhaps offer to codegen based off my local model first, if i accept the risks of mismatch between the model i have on my machine and the model i have in the cloud.

Describe alternatives you've considered

do nothing

[AaronZyLee]

The main reason for this is that the new schema is not compiled. A temporary solution is to run amplify api gql-compile after changing the schema and then it is all good to run amplify codegen. I will soon create a PR for graphql compiling check when running codegen.

[pagameba]

If I run the indicated commands, it still doesn't seem to update the generated code in src/graphql although the compile step does seem to know about the changes - just codegen doesn't do anything as far as I can tell.

[SwaySway]

Re-opening as we are reconsidering the implementation. As of now the current workaround when making schema changes, you can run amplify api gql-compile && amplify codegen.

[binadamu-isiyoonekana]

@SwaySway Hi Josue. Any progress on this subject, as with latest version of Amplify (namely 4.41.0), nothing is generated/updated in src/graphql folder (i.e mutations, queries, ...) when entering amplify api gql-compile && amplify codegen. Thanks and Happy New Year !

[SwaySway]

@binadamu-isiyoonekana
Could you provide your .graphqlconfig.yml and the schema? If the schema contains sensitive information you can send it to our email amplify-cli@amazon.com

[vincent38wargnier]

I have exactly the same issue. I'm using codegen for months, and suddenly today it's not generating the code even if it's saying it's doing it :

And the Schema is well updated :

This is the graphql code I added to the API :

type NewsLetterSubscribers @model @auth(rules: [
  {allow: private, operations: [create]}
  {allow: public, operations: [create], provider: iam}
  {allow: public, operations: [read, update, create], provider: apiKey}
  ]) {
    id: ID!
    subscribed: Boolean!
    email: String!
    dateUnsubscribed: AWSDateTime
    reasonUnsubscribed: String
}

I have CLI version 4.44.0 on macOS

[vincent38wargnier]

I made some tries with the mock, creating news tables, and looking at the same time what is happening in the mutation.js file.

It happens that at some point during the code génération the code of the new tables is created, but it's removed right away, I don't know why.

At this point the new code is created :

And at this point its removed :

This is all the things I have in my console :

So first line creates the code, and the second indentical line removes it. I don't know what to understand from that. It seems that an instance of the API is stucked in the codegen system, so the codegen does its work properly, and then the old instance does its work as well, so the code generated at the end is related to the API before the bug appeared.

But apparently removing the .graphqlconfig.yml file solves the pb. Thanks to aws-amplify/amplify-cli#50 (comment)

Btw removing, or reinstalling codegen didn't change anything

[nubpro]

Re-opening as we are reconsidering the implementation. As of now the current workaround when making schema changes, you can run amplify api gql-compile && amplify codegen.

This workaround you proposed does not seems to work.
src/graphql doesnt get updated after running the command you suggested, however schema.json is. Tested on 4.44.0

.graphqlconfig.yml

projects:
  amplifyreact1:
    schemaPath: src/graphql/schema.json
    includes:
      - src/graphql/**/*.js
    excludes:
      - ./amplify/**
    extensions:
      amplify:
        codeGenTarget: javascript
        generatedFileName: ''
        docsFilePath: src/graphql
        maxDepth: 2
extensions:
  amplify:
    version: 3

schema tested:

type Todo @model {
  id: ID!
  name: String!
  description: String
  test6: String <--- change this field name
}

[nubpro]

A little update:
I deleted my .graphqlconfig.yml and did amplify codegen add, it generated a new .graphqlconfig.yml with the following content:

projects:
  amplifyreact1:
    schemaPath: amplify/backend/api/amplifyreact1/build/schema.graphql
    includes:
      - src/graphql/**/*.js
    excludes:
      - ./amplify/**
    extensions:
      amplify:
        codeGenTarget: javascript
        generatedFileName: ''
        docsFilePath: src/graphql
        region: ap-southeast-1
        apiId: null
        maxDepth: 2
extensions:
  amplify:
    version: 3

Noticed that schemaPath changed and inclusions of several new settings.

Afterwards, I ran amplify api gql-compile && amplify codegen, it now works as expected.
Is there a reason as to why this had happened?

[siegerts]

Hi All, Thanks for keeping this updated and re-raising 🙌🏻 .

The team is looking into this now to determine the best path forward, and will update this as soon as there is more information.

Just an fyi - this will be transferred over to the amplify-codegen repo for better tracking (once permissions are set).

Thanks again!

[ankitmhn]

Is there a fix or some workaround for this? I'm still facing this issue.

[nubpro]

Is there a fix or some workaround for this? I'm still facing this issue.

#113 (comment)

[phani-srikar]

The workaround is to re-compile your updated schema as mentioned here: #113 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if you are still encountering problems.

[Robbie-Cook]

Why in the name of all that is holy, do I need to use amplify api gql-compile && amplify codegen instead of just amplify codegen ffs

[isaac-rosterlab]

Why in the name of all that is holy, do I need to use amplify api gql-compile && amplify codegen instead of just amplify codegen ffs

To take it one step further, why not: "amplify api gql-compile && amplify codegen && amplify codegen models" instead of just "amplify codegen". Also, this workaround should probably be entered in the docs somewhere.

[pencilcheck]

After doing all those latest answer with new scripts, the model which are renamed in the cloud didn't get synced to the local JS files. All models created are synced but the existing models renamed are not replaced.

[cjsilva-umich]

Three and a half YEARS later and the behavior is still not like the docs...

At least the mentioned workaround does the trick sometimes.