Atomic Operations about prisma-appsync HOT 2 CLOSED

With Atomic Operations, the GraphQL structure will probably have to differ slightly from Prisma Client API. One clean way to differentiate atomic operation from classic updates could be something like this:

mutation {
  updateManyPosts(
    operations: {
      views: { increment: 1 }
    }
  )
}

Then add a custom validation in Prisma-AppSync Client to prevent using both operations and data at once.

How did you implement it on your end?

from prisma-appsync.

I implemented it similar to how prisma does it, but that does the problem I mentioned where id have to use "set:" when adding a value. Your way sounds great with a good validation, alternative would be to have a different resolver itself?

I think your idea would work best for more consistency with create and update.

from prisma-appsync.