Add top-level `context` to services

From my quick pseudo code from our call:

import { PrismaClient } from '@prisma/client'
import { RedwoodContext} from '@redwoodjs/api'

const db = new PrismaClient()
const context = new RedwoodContext()

export const posts = () => {
  return db.post.findMany()
}

[chris-hailstorm]

Here’s a simple example that seems to work – adds indicated:

/* api/src/functions/graphql.js */

import {
  createGraphQLHandler,
  makeMergedSchema,
  makeServices,
} from '@redwoodjs/api'

import importAll from '@redwoodjs/api/importAll.macro'

import { db } from 'src/lib/db'

const schemas = importAll('api', 'graphql')
const services = importAll('api', 'services')

// new
const context = ({context, event}) => {
  console.log('GraphQL custom context handler')
  console.log(context)
  console.log(event)
  return context
}

export const handler = createGraphQLHandler({
  schema: makeMergedSchema({
    schemas,
    services: makeServices({ services }),
  }),
  context,  // new
  db,
})

Now I’m trying to figure out how to get more info into the context from the client side.

[peterp]

@chris-hailstorm The event contains a bunch of useful things, but I think mostly the way of getting stuff from web -> api (especially authentication tokens) would be to add them to the headers of apollo graphql client.

I need to look into how we do that via the Redwood Providers. It may not be technically possible right now, but I need to double check that.