I've been looking into creating a unique dependency injection scope for certain levels through the execution process. ie a type resolver scope similar to a singleton, request, or session scope so my data fetchers can inject things with the right lifecycle.
So I'm wondering if there's any good ways to hook into the execution process to define clear scoping bubbles around each resolver?
I've been looking into creating a unique dependency injection scope for certain levels through the execution process. ie a type resolver scope similar to a singleton, request, or session scope so my data fetchers can inject things with the right lifecycle.
So I'm wondering if there's any good ways to hook into the execution process to define clear scoping bubbles around each resolver?