Michael

Ah, I see what you mean. This is a limitation of the request mapping template currently as the result of the evaluated template is expected to be a JSON object...

Thank you for your comment. This feature request is in the backlog but I have noted this feedback for prioritization.

Hey @jbonigomes, I'm taking a look now. It's been a while since I've updated these dependencies. I'll let you know when its fixed :) In the meantime, here is a...

@djkingh01 Currently the @model directive expects to contain a single data type, however, we are looking at generlizing this to allow overloaded indexes & multiple types per table but there...

@djkingh01 For now, yes, you would have to implement everything yourself. We do want to support the use case where you can adopt an existing table for an @model type,...

This sounds very similar to custom authorizers which would allow you to write custom logic to fulfill the identity for your request. You would be able to use the same...

I'm having a similar problem linked here https://github.com/sveltejs/sapper/issues/1074. Currently working on a fix.

To get a set of values based on id, you should use the BatchGetItem resolver operation as outlined here https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-dynamodb-batch.html. This is currently a bit tough to use when using...

Thanks for the feedback. I will record this feature request so that it can get prioritized. Philosophically there is no reason we can't support batch operations out of the box...

Agreed. We can add a parameter that users can set after the fact without too much trouble. We should also add this as part of the `amplify add api` command....