Injecting different header data on each request?

I know that it’s possible to send extra headers when converting OAS to GraphQL by using https://github.com/strongloop/oasgraph/tree/master/packages/oasgraph#options, but this seems like it will only set it up once. And that’s great if you want to add static header, but what about something that would change on every request? Is it possible to inject something which could change on every request? In my instance I need to pass the Authorization header which more than likely to change on every request to the ‘/graphql’ end point.

My code currently looks a little something like:

module.exports = async function () {
    const app = express();

    // This will always be sent for every request and is static
    let oasOptions = {headers: {'X-Origin': 'GraphQL'}};

    // Would seem that this is a one-time thing done when Express kicks in?
    // The header is likely to be different on every call express takes, though.
    if (app.request.headers && app.request.headers.authorization) {
        oasOptions.headers.authorization = app.request.headers.authorization;
    }

    // I have an NPM package that handles using oasgrah
    const schema = await oas.toGraphQL(oasOptions);

    app.use(cors());
    app.options("*", cors());
    app.use(express.urlencoded({extended: true}));
    app.use(express.json());

    // I need to inject to the resolver every time this is called
    app.use(
        "/graphql",
        graphqlHTTP({
            schema,
            graphiql: process.env.NODE_ENV === "local"
        })
    );

    return app;
};

Apologies if I’ve missed something obvious in the docs or mis-understood how the options bit works.

[Alan-Cha]

@amnuts Wow, thank you so much for the follow up! This is beyond cool! It is also very well documented! I will definitely check it out later but I already left it a Github star 😄

If you do make a blog post, please let us know as well! It would be interesting to see what your user experience was like so we know what to improve on in the future!

[amnuts]

@Alan-Cha @ErikWittern I’ve been able to make public our usage of oasgraph that I mentioned, if you fancy checking it out; https://github.com/elucidat/elucidat-npm-skeleton

Hoping to write a blog post about it at some point and how easy it was to achieve with oasgraph.

Thanks for the excellent library and support!