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
Firstly, thanks for this tool. It's been really great to have my resolvers strongly typed with minimal effort. I've recently been trying out a new modular pattern which has led me to a problem.
Problem
When I use extend to break up my type definitions I don't see the extended values in the type.
Example
Prior to splitting the modules out I have a TypeScript type that accurately describes the resolvers for Query.
Ideally I want to see something like below. Is this possible? If not is there a reason the extended types shouldn't be concatenated together?
If it's not currently possible, and it's not a terrible idea would you be open to a PR?
Firstly, thanks for this tool. It's been really great to have my resolvers strongly typed with minimal effort. I've recently been trying out a new modular pattern which has led me to a problem.
Problem
When I use
extend
to break up my type definitions I don't see the extended values in the type.Example
Prior to splitting the modules out I have a TypeScript type that accurately describes the resolvers for Query.
But as I want to add more to the schema I look to add something like:
Which of-course isn't valid, as I've now defined Query twice.
To keep the code nice and clean I give the Query a base definition, and use
extend
in the seperate modules:However, now the Query definition shows only
_empty
and not the extended values:Ideal
Ideally I want to see something like below. Is this possible? If not is there a reason the extended types shouldn't be concatenated together?
If it's not currently possible, and it's not a terrible idea would you be open to a PR?
The text was updated successfully, but these errors were encountered: