You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just trying to make sure I understand correctly, but it seems that when using DI, all resolvers are acquired through DI in addition to needing to be provided explicitly to buildSchema({ resolvers }). If I provide a container for DI and don't mark all of my resolvers with @Service(), I get errors that they can't be located by DI. As an extension of this, using middleware alongside DI containers requires me to use class-based middleware. Is all of that accurate?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Just trying to make sure I understand correctly, but it seems that when using DI, all resolvers are acquired through DI in addition to needing to be provided explicitly to
buildSchema({ resolvers })
. If I provide a container for DI and don't mark all of my resolvers with@Service()
, I get errors that they can't be located by DI. As an extension of this, using middleware alongside DI containers requires me to use class-based middleware. Is all of that accurate?Thanks for a terrific library!
Beta Was this translation helpful? Give feedback.
All reactions