graphql-stitching-ruby icon indicating copy to clipboard operation
graphql-stitching-ruby copied to clipboard

GraphQL Schema Stitching for Ruby

Results 10 graphql-stitching-ruby issues
Sort by recently updated
recently updated
newest added

At present, executor batching inlines all stitching IDs into their resolver queries: ```graphql query MyOperation_2 { _0_result: widgets(ids:["a","b","c"]) { ... } _1_0_result: sprocket(id:"x") { ... } _1_1_result: sprocket(id:"y") { ......

enhancement

Similar to other composer libraries, there should be some controls for prioritizing and hiding elements in a schema. Specifically: * `@override`: prioritize a field from a given location. This can...

feature

GraphQL foreign keys are commonly handled as `Product.imageId` is here: ```graphql # -- Products schema: type Product { id: ID! imageId: ID! } # -- Images schema: type Image {...

feature

It'd be nice to formally support field-level authorization through the query planner, similar to other federation libraries. A few specs: - Unauthorized fields are simply filtered out of the request...

feature

GraphQL Ruby supports [visibility controls](https://graphql-ruby.org/authorization/visibility.html) for selectively hiding parts of a schema from view. Stitching should be able to piggy-back on the GraphQL Ruby implementation of the feature to allow...

feature

Fixes for skip/include handling, and rolls back some unreleased empty set cases explored in https://github.com/gmac/graphql-stitching-ruby/pull/177.

Reorganize formatting hooks (composition mergers, error formatters, etc) into a concern that can be added to various objects. All output formatting methodology is now centralized on one object, and allows...

Includes: * Client formatting hooks #187 * Authorization controls #182