Zeyu Li

> In DataStore, we get the authtypes based on `.read`. Since developers can use this schema with DataStore as long as they allow listen and sync. then this code probably...

I notice you have `IAM Authorization` in the bad code which is missing in the correct code. Do you have any admin roles defined in the file `custom-roles.json` which is...

@raphkim I am not sure whether this is a bug. According to the [amplify doc](https://docs.amplify.aws/cli/graphql-transformer/connection#belongs-to), we only support explicit use case for `belongsTo` in a bi-direction connection, which is applied...

@raphkim Not sure if the expected code snippet is correct. I try to make some code changes but find this part: https://github.com/aws-amplify/amplify-codegen/blob/588b9e4da7e40639bdb0d5cf346abd6ce3a0df5d/packages/appsync-modelgen-plugin/src/visitors/appsync-visitor.ts#L458-L459 So the `targetName` field is originally designed to...

The `elasticSearch` naming properties are expected as the current `searchable` in amplify does not fully migrate to the opensearch module yet, which still stays on the ElasticSearch 7.10. This results...

From the description, it is most likely that the failure of the deployment is caused by this > I made this change, along with a few other updates to amplify.json...

I am able to repro the issue with the following schema. Mark it as a bug. ```GraphQL enum Completed { YES NO } enum Priority { LOW MEDIUM HIGH }...

It turns out to be related to the CDK bug https://github.com/aws/aws-cdk/issues/26838

@TheDutchCoder Thanks for putting this out. It looks like a bug for the type generation of graphql operations. I will look into this and make a fix soon

@amondnet Thanks for the contribution. It is normal that the generated files does not fully follow the lint rules as it is commented at the beginning of the file. However,...