Join GitHub today
Support remote graphql schemas in plugins #4870
Allow a plugin to link a remote graphql API into the main reaction graphql API via remote schema delegation/stitching. This capability will support our long-term architecture vision of independent-but-integrated services.
The main implementation comes from
My solution here is to widen the feature set of our plugin
I believe there are no breaking changes here. Quick local testing looks like the reaction meteor app still functions fine.
My test case for this is using a pre-generated schema for the remote service, and thus I can load the plugin synchronously into reaction. It is likely that enabling plugins to perform asynchronous initialization tasks would be convenient, but it's not strictly necessary for the work at hand, so I'm leaving it as a separate feature to implement, but it's worth thinking about a bit now. For example, a plugin might want to introspect the remote graphql service's schema over the network at runtime instead of generating an SDL file and bundling that with the plugin. At the moment, that configuration would not be supported.