graphql-hive / graphql-hive/graphql-modules

Per-message ProviderScope for Websockets

Open
#1,218 0 comments 0 reactions 0 assignees View on GitHub
legacy
Dominant language
TypeScript
Stars
1.3k
Forks
113
Avg merge
3h 36m
Merged PRs (30d)
1

Description

It looks like `ProviderScope.Session` is kept on memory for the whole ws life, while instead I need to create a new instance on each ws message in order to be able to use Mikro-ORM with graphql-modules and ws transport: https://github.com/accounts-js/accounts/pull/1003#issuecomment-651710092

I'm creating an Accounts.js adapter for Mikro-ORM and I would like to share the same `EntityManager` provider (which takes care of forking it on each network request/ws message) with the Accounts.js authentication module, so that the Identity Map gets shared.

Is there anything graphql-modules provides in order to restric the lifespan to ws messages when using a ws transport?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.