graphql-schema

for mutations/queries you can access request object like so

    @strawberry.query
    async def sync_job(
        self, info: Info
    ) -> t.Optional[sync_job_.SyncJob]:
        user = info.context.request.USER

subscriptions are inconsistent as you need to access the request old style

    @strawberry.subscription
    async def sync_job(
        self, info: In

probably for the entire pipeline.

I think it would be super useful if one could include headers when defining the endpoints.

Something like:

endpoints: [{
  namespace: 'model',
  typePrefix: 'Model',
  url: 'http://localhost:8080/graphql' // url to a GraphQL endpoint,
  headers: {
    'Authorization': 'Bearer **********************',
    'content-type': 'application/json'
  }
}

https://github.com

Add a GitHub action flow for publishing a new version (run build, run tests, publish to npm and GitHub packates) etc.

https://github.com/sisense/graphql2rest/actions/new

Seeing some posts about subscriptions on Reddit about game development, I wanna explore options for building multiplayer games with live queries 😉