You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of our graphql queries are wrapped in the same object name, so if a component is running multiple queries I don't know of a way to pass each individual resolver to that corresponding query.
Here is an example query, and all of our queries are done this way. It's grabbing account information for our claimant, then returning the data in an object like this:
However, in multiple sections I'll be grabbing claim information as well as incidents or alerts, and I don't know a way to send multiple resolvers that signify each query when all go into the account object. I kinda like this repository, but as I was implementing this I noticed this issue along the way, and don't know I should do.
The text was updated successfully, but these errors were encountered:
roninMo
changed the title
Point Each Resolver to a specific function
signify which resolver corresponds to a specific query
Jan 13, 2022
All of our graphql queries are wrapped in the same object name, so if a component is running multiple queries I don't know of a way to pass each individual resolver to that corresponding query.
Here is an example query, and all of our queries are done this way. It's grabbing account information for our claimant, then returning the data in an object like this:
However, in multiple sections I'll be grabbing claim information as well as incidents or alerts, and I don't know a way to send multiple resolvers that signify each query when all go into the
account
object. I kinda like this repository, but as I was implementing this I noticed this issue along the way, and don't know I should do.The text was updated successfully, but these errors were encountered: