N

icon location Developer, academic

Results 28 comments of N

@aws-appsync/eslint-plugin not compatible with eslint v9

+1

@aws-appsync/eslint-plugin not compatible with eslint v9

Confirmed. I was able to do the same with V2. Thanks!

Conflict Detection with Optimistic Concurrency does not return the current version of the object

I currently have too many override resolvers that are used not to add special functionality but just to patch little issues. Each of these I will then have to manage...

The implementation of the nullish coalescing operator (??) in AppSync_JS resolvers is not consistent with JS (Gen2)

Hey @AnilMaktala , thanks for your reply! Is it that I need to file a support case to get it on the roadmap or just to get unblocked? As a...

Use AppSync JavaScript resolvers by default instead of VTL in Gen2

+1 We have found ourselves rewriting some of the same logic in JS to make simple adjustments in order to avoid working with VTL. For us, working with VTL was...

[Feature Request]Add an option of ProjectionType for Dynamodb Global Secondary Index (Amplify Gen2)

+1 Same situation. I have indexes that only need a few fields projected and would like to avoid the storage and cost waste. **Workarounds explored:** There is a way to...

[Feature Request]Add an option of ProjectionType for Dynamodb Global Secondary Index (Amplify Gen2)

There's also the (less than ideal) workaround to [define the table using the CDK](https://aws.amazon.com/fr/blogs/devops/a-new-and-improved-aws-cdk-construct-for-amazon-dynamodb-tables/) and attach it as a data source. It's not clear to me how nicely this will...

[GEN2 backend]Jest testing issue: No context value present for amplify-backend-namespace key

I'm also running into this while testing with Vitest. Hopefully there'll be some guidance on this.

Circular Dependency Issue in our Amplify CI/CD pipeline

I upgraded to 11.0.3. I now have this issue.

Circular Dependency Issue in our Amplify CI/CD pipeline

I was able to use the stack resources to track down the conflicts. I found that there were resolvers that were referenced in the pipeline of sibling stacks (eg. createdBy,...