-
### Expected Behaviour
When accessing the router.context in a resolver, with async resolvers, it should not be an empty dict, but much rather expose the context injected with app.append_context[](u…
-
### Is this feature request related to a new or existing Amplify category?
_No response_
### Is this related to another service?
Appsync JavaScript resolvers
### Describe the feature you'd like t…
-
It is possible for resolvers to become detached when an incorrect schema is deployed and correcting the schema does not reattach the resolvers. In addition this issue can ripple to affect other resolv…
-
### Describe the feature
The `aws_appsync` module does not include any L2 constructs to enable caching at the API level. There is a `CachingConfig` construct but that is specifically for resolvers an…
-
Hi, are you planning to add support for Pipeline Resolvers in unit testing soon? Expressions like previous.result are not working right now.
-
### Description
Add support for AWS AppSync environment variables
### Affected Resource(s) and/or Data Source(s)
* aws_appsync_graphql_api
### Potential Terraform Configuration
```terra…
-
I have created a form using Nextjs + AWS Appsync API, I want to embed that form into another website (WordPress) , While submitting the website send a status code 401, I have not set up a cors policy …
-
I'm having some trouble using the `@aws-appsync/utils` (v1.8.0) in my Vitest tests. Given the following test script `util` is equal to `{}`;
```ts
import { util } from '@aws-appsync/utils';
imp…
naedx updated
2 months ago
-
### Describe the feature
In 2022, AppSync launched support for Code-based resolvers, initially supporting Javascript runtimes. https://docs.aws.amazon.com/appsync/latest/devguide/resolver-reference…
-
### Amplify CLI Version
12.2.3
### Question
_No response_