Schema stitching and transforms to remove ID pointers

[wabrit]

With reference to the example of Chirps and Authors outlined here, I want to hide the Chirp.authorId field from API clients so that they only see the "stitched" field Chirp.author.

Having attempted this with a bespoke schema transform it appears not to be possible as the fragment needed for the stitching relies on authorId. Have I missed something, or is there an alternative approach; having both fields exposed seems a bit of an anti-pattern.

[yaacovCR]

Filtering out specific fields of objects, that has been requested in #819, with pending pull request #964, but no recent traction...

[wabrit]

Thanks - yes I saw that PR. The problem isn't the lack of such a filter, but the fact that it can't be applied to a field used as the fragment id in stitching without breaking stitching itself.

[yaacovCR]

I haven't actually used that transform myself, as it is not yet been merged. but I would think either (a) merging the transformed schema and then delegating to the original schema or (b) transforming the merged schema would work... Are you able to share the code you have worked on so far?

[yaacovCR]

Ah, I think I get why (a) doesn't work. What about (b)?

[yaacovCR]

In particular, I mean something along the lines of

transformSchema(mergeSchemas(...), [myFilteringFieldTransform])

[yaacovCR]

In graphql-tools-fork, you can do this without another delegation layer with just filterSchema({ schema: mergeSchemas(...), ...options }).

Progress!

[yaacovCR]

Type merging is better solution, see #1306