-
### 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…
-
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…
-
Our project has a lot of async-resolvers. This makes it difficult to build an optimal graph because we are unable to use an async-fields for further resolutions. Discussion [here](https://github.com/M…
-
### 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…
-
What is the recommended method for testing a custom resolver with nexus? Currently the below code is harder for us to test, so we ended up passing the call to our previously existing resolvers that we…
-
![image](https://user-images.githubusercontent.com/8760590/136486908-18cb9b54-2bb7-4f73-9ff7-8c227c956b23.png)
-
Noticed that I hadn't wrote about this yet but it's something I really want from GraphCMS that's missing currently.
It'd be nice to be able to define custom resolvers when fetching data. When you'r…
-
May I suggest you add more information about the functionality of graphql-compose-connections. At least for me, connection reminds of relay. Since I'm not using relay, I feel I have no use for 'conne…
-
Need to find a way to automatically combine resolvers instead of adding them to `src/server.js`
-
Similar approach to https://github.com/antfu/unplugin-vue-components#importing-from-ui-libraries
I been using this pattern for `unplugin-vue-components` for a while and I think it turns out a flexi…
antfu updated
3 years ago