Issue with Types when stitching schema about schema-stitching-handbook HOT 5 CLOSED

Sounds about right! Is Stitching starting to make more sense now with some concrete examples? I personally find it to be fairly intuitive given that the subservices are all plain GraphQL, versus Federation where there’s a bunch of magic happening at every layer of the stack to bring it all together.

from schema-stitching-handbook.

I guess I don’t follow the problem here. Looks like you haven’t converted the example into typescript, which I assume you are using? These examples are plain JavaScript. You’d need to add casting information as appropriate to your version of TypeScript. I’m intentionally using JavaScript as a lowest-common denominator.

Please let me know if I’m missing something else here that is technically inaccurate in the example.

from schema-stitching-handbook.

@gmac Thanks for the clarification. I assumed that it was compatible with Typescript out of the box. Will fix it on my end then 👍

from schema-stitching-handbook.

@gmac Btw, I just had to mark the return type as AsyncExecutor and the error above went away 🎉

import { AsyncExecutor } from '@graphql-tools/delegate';

const makeRemoteExecutor = function(url:string) : AsyncExecutor {
  return async ({ document, variables }) => {
    const query = typeof document === 'string' ? document : print(document);
    const fetchResult = await fetch(url, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        query, variables
      })
    });
    return fetchResult.json();
  };
};

from schema-stitching-handbook.

@gmac Stitching - Yes, Typemerging - In Progress . While I understood the concepts properly with both of ur help and have it setup as part of the stack, I am working to see how I can fit it for my usecases. Will share my progress as I go along.

from schema-stitching-handbook.