Hello everybody, Just to ask if anybody have already tried to do some graphql-binding with auth (I don't even know if it's possible for now). My goal is to provide a clean way to request my graphql api on another backend, and, because otherwise is too easy, I need to provide auth token on queries/mutations and subscriptions! Thanks for your feedback on this 🙂

grapqhl-yoga

exposes

express

as a root key like

server.express

which you can use for any kind of middleware. this will not work for subscriptions. https://github.com/LawJolla/prisma-auth0-example check that out

@woss Sorry if was not clear, I'm trying to consume a graphql api on a backend (and not building a graphqlapi) But don't worry, I will try by myself ^^ Just would like to know if someone have any xp with this kind of setup

My goal is to provide a clean way to request my graphql api on another backend,

that seems like an API to me 🙂

arf, I'm trying again ^^ On my backend (REST), I want to request my graphql endpoint. To explain a little bit more, the backend need to subscribe to a subscription for some business requirement. For now I have set a classic

apollo-client

but it's a little bit painfull for my collegue, he don't really like to have 50lines just for set the client (ws + http + auth links) and also to give a simple string (graphql query) to have some data. My best idea for now is to try something with

graphql-binding

to provide a "clean way" to interact with this graphql api. I just need to see how to setup this one to add the

auth-token

in the websocket and http requests 😉

@tim2 can you provide a few pointers?

const {
  introspectSchema,
  makeRemoteExecutableSchema
} = require("graphql-tools");
const { HttpLink } = require("apollo-link-http");
const fetch = require("node-fetch");

const { Binding } = require("graphql-binding");

(async () => {
  try {
    // Create the executable schema
    const uri = "<http://localhost:6020>";
    const link = new HttpLink({ uri, fetch });
    const schema = await introspectSchema(link);
    const executableSchema = makeRemoteExecutableSchema({
      schema,
      link
    });

    // Create the binding
    const questionnaireAPI = new Binding({ schema });

    questionnaireAPI.query
      .questionnaire({ nisId: 2182 }, '{ id }')
      .then(console.log) // -> null
      .catch(console.log);
  } catch (e) {
    console.error(e);
  }
})();

My current progression (I'v disabled the auth for now, just to have only one problem ^^) no more error, but my query is not working…

Thanks for bringing this up @fabien0102,

graphql-binding

is exactly the right approach

Nice, exactly my current page before your response ^^

we're releasing a new api this week, maybe even today

Any example for injecting the header after?

we just recommend to you right now creating your own link

oki, I will try

you can have a look at how we're doing that in the prisma binding https://github.com/graphcool/prisma-binding/blob/master/src/Prisma.ts#L24

Perfect 👌

Oh ok, thanks for finding the issue & documenting it!

Totally normal ;) Meeting Time for me... I will continue tomorrow ;) thx for your support

Since it's an Apollo Link, you should be able to add setContext with the authentication header

I saw 😉 Thanks for support BTW, @tim2 Ideally I would like something more abstract: 1.

graphql-codegen-binding ... -t MyService.js

2.

import { MyService } from "./MyService"

const myService = new MyService({endpoint: "", secret: ""})
// start playing \o/

Is it something in the roadmap for this kind of implementation or should I start to fork 😁 ?

@fabien0102 you have the exact right timing! I'm releasing some stuff around that, especially the new github example binding. That will be available in about 30-60min, stay tuned!

Oh yeah! 👌

@fabien0102 see https://github.com/graphql-binding/graphql-binding-github/tree/beta#codegen / contributors channel 🙂

Nice! I finish my "real tasks" and play with this ^^