Greg MacWilliam
Greg MacWilliam
FWIW, I wrote these sorts of validations for the Node GraphQL Tools schema stitching package, and landed on the following rules: - boundary scalars are fine as long as they’re...
To distill this down to a basic 2.0 spec, my suggestion would be: - Custom scalars are allowed to appear across services, and they shouldn’t require a boundary declaration. They’re...
That’s a fair point on the input divergence also being blocking. I know GQL Tools handles this by always filtering inputs to the subservice schema, but I don’t love that...
Hmmm. What are you referring to as a boundary accessor? A root accessor specifically used for federation access, or any object field in the graph that relates to a boundary...
One other though here related to https://github.com/movio/bramble/issues/109: it'd be a lot more flexible for integrators if the accessor argument name was read from the schema the same way the field...
Related: https://github.com/movio/bramble/issues/98
Huge +1, especially on the end state of Bramble having a defined cartridge format. As part of this objective, I'd suggest the following core APIs: * `ComposeExecutableSchema([{ServiceURL string, SchemaSDL string,...
Hey, in v8, can we set batch to true on merged type config? Feels like the better default at this point.
Wooo, in-house pubsub? That’s exciting.