aws-appsync-community icon indicating copy to clipboard operation
aws-appsync-community copied to clipboard

The AWS AppSync community

Results 175 aws-appsync-community issues
Sort by recently updated
recently updated
newest added

Hi, I want to unit test my resolvers but when I provide a context object with an identity object that is formed according to cognito userpool authentication, I get the...

feature-request

I tried to convert my object keys from string to numbers, but got "The code contains one or more errors. " as a response when I tried to use `parseInt`,...

feature-request

I have items coming from DynamoDB. When a field is a number then when I use something like ```ctx.result.num + ""``` the result is ```"null"```. For example, I have a...

pending triage

Hi, I am currently using AWS Lambda with AppSync, and I want to versionize my Lambda. However, when I try to do so, I encounter an issue where I am...

pending triage

we are currently working on a critical project that involves integrating our OpenSearch cluster with appsync resolver to enable seamless data retrieval and processing from our grapql API. Currently we...

feature-request

For example, there is a type for `HTTPRequest` but not one for `HTTPResponse`. It's easy enough to type yourself, but it was hard to find in the [docs](https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-http-resolvers.html) what the...

feature-request

When trying to type just the result of the backend request, you need to specify several irrelevant types which makes the resolver verbose and hard to grok at a glance....

feature-request

Hi! This is a feature request for returning the field name when there is some syntax error in a mutation. **Current Behaviour** Given we have the following schema ``` mutation...

feature-request

Do you want to request a feature or report a bug? Bug What is the current behavior? Spread operator does not work to pass arguments to util.appendError. This causes an...

bug

Since `throw` statements are not allowed in AppSync JS, there should be a `no-throw` rule to detect and report any `throw` statements

pending triage