search

enisdenjo / graphql-composite

Spec agnostic GraphQL composite schema planner, executor and explainer.
MIT License
7 stars 0 forks source link

Support interfaces implementing other interface(s) #27

Open enisdenjo opened 5 months ago

gmac commented 1 month ago

Is there some advanced planning or execution concern here? This is a small consideration while expanding interfaces out to their possible type implementations in the "Blueprint" as you call it, but beyond that, it should just work in planning and execution, assuming basic interfaces are implemented correctly? Curious if you've thought of something I'm missing.

enisdenjo commented 1 month ago

Haven't really though about it. I know that an interface can implement another interface in the spec, so am just having this issue here to make sure it works in the future.

gmac commented 1 month ago

Cool. In my experience you just have to expand the range of the resolver mapping with nested interfaces; then basic interface handling does the rest by expanding concrete types for interfaces not in the entrypoint location.