Dane Pilcher

Marking this as a request for an enhancement.

To confirm, you have added `src/graphql/customQueries.ts` as an `excludes` pattern to your `.graphqlconfig.yml` file?

I wasn't able to reproduce this. Can you share your `.graphqlconfig.yml` and GraphQL schema? If you do not want to share your schema publicly you can use `amplify diagnose --send-report`...

I wasn't able to reproduce with any multiline comment, but I could reproduce if the comment included backticks (`` `some text` ``). In fact, any usage of backticks would result...

`interface` is not currently supported for the Amplify GraphQLAPI or the codegen utilities.

I was able to reproduce this issue. This will be resolved for customers using Amplify JS library V6 with https://github.com/aws-amplify/amplify-codegen/pull/799. An additional fix is needed for V5 customers.

I was able to recreate the issue with the following schema. ```graphql input AMPLIFY { globalAuthRule: AuthRule = { allow: public } } # FOR TESTING ONLY! type BasicModel @model...

We have not had the time to prioritize this issue. Please use the workaround in the meantime. We would also accept an external contribution to resolve this if anyone wants...

Thanks for the contribution @MorFix. Could you also add this test schema here: https://github.com/aws-amplify/amplify-category-api/blob/main/packages/amplify-graphql-schema-test-library/src/index.ts#L39 This will add this schema to our E2E tests that will test for successful compilation of...

A new version of amplify-codegen has been released with the change from aws-amplify/amplify-codegen#248.