-
### Before opening, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-js/issues?q=is%3Aissue+) and [discussions](https://github.com/aws…
-
### Which packages are impacted by your issue?
@graphql-codegen/typescript-resolvers
### Describe the bug
Is there a reason why we don't use the resolver types for all non scalar properties? cc @ed…
-
We use fastapi and strawberry to utilise the power of asyncio. However, our asynchronous graphql resolvers perform synchronous database calls which block the event loop. This means that while the API …
-
**Is your feature request related to a problem? Please describe.**
Managing change within a schema over time. Schema evolution is a common pattern that is used. But creates complications and head…
-
### 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…
-
Currently, `composeResolvers` mutates the `resolvers` argument. I am requesting that this behaviour be changed in a future major version, or add a setting so it can be set to not mutate.
-
User is logged in on apple iphone. Requests a service agreement. On sending the attached is seen and received by text message.
Render shows this in the log:
t","date":1724822696,"to":"+61494140390",…
-
### What happened?
Currently to create a resolver for field you have to explicitly set this in the config file like this
```
Todo:
fields:
user:
resolver: true
```
### What d…
-
### Amplify CLI Version
12.10.1
### Question
To enhance the flexibility of Appsync, we are investigating the migration from VTL resolvers to JS resolvers. Despite consulting the documentation for i…
-
**Describe the bug**
The current way of looking up a logical resolver for a scheme does not allow for `+` schemes; example if the `jar+file:///` scheme was implemented with a logical resolver for t…