info.path between multiple stitched local subschemas

[maxbol]

Hello!

In a stitching model with several local subschemas, and given a query that traverses multiple layers of delegation, as such -

{ 
   a { # Subschema A, resolved by Query.a
      b { # Subschema B, resolved through type merging by Query._a
         c { # Subschema C, resolved through type merging by Query._b
            path # Subschema C, field resolver resolves to info.path
         }
      }
   }
}

path will naturally resolve to _b.path (without batch loading). Is there any way to make it resolve to a.b.c.path, or any other reasonable way to pass on the full path of a specific field from the gateway schema to subschema resolvers?

[yaacovCR]

Do you mean in a subschema resolver? That the info argument should have a different path cognizant of the gateway?

[maxbol]

Not saying it necessarily should, but being able to retrieve the full gateway schema path to the resolver within the subschemas resolver function is the problem I am trying to solve at the moment, yes! Was curious to see if there would be any sane way to do it. tis 11 maj 2021 kl. 18:23 skrev Yaacov Rydzinski ***@***.***>:

…

Do you mean in a subschema resolver? That the info argument should have a different path cognizant of the gateway? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2946 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI7Q7PRIKLNJZP5EQS2A7TTNFKWVANCNFSM44VYBDPQ> .

[maxbol]

Ah, hadn't thought abt that. But that would only work with remote subschemas, yes?

[ardatan]

Executors can be used against the local schemas as well.

[maxbol]

Interesting, is there an example implementation of that somewhere that I could look at?

[yaacovCR]

See near

graphql-tools/packages/delegate/src/delegateToSchema.ts

Line 239 in 41a4dc7

execute({

where default executor for local schema defined, modify as necessary

[maxbol]

Much appreciated!