Proposal (v2): Injector should implement context.Context

[diamondburned]

Currently, do provides a Shutdown API for shutting down which can perform I/O or long-running operations, and ShutdownWithContext exists to allow the user to pass their context down to those operations. However, there isn't a Start equivalent for initializing services. As a result, the constructor is the only place to perform service initialization.

A problem arises when the constructor also tries to perform I/O or long-running operations, such as connecting to a database. There isn't a way to pass the user's context to those operations during construction. In my opinion, the easiest solution to this problem would be to:

1. Make do.Injector also implement context.Context, and
2. Add func do.InvokeContext[T](context.Context, do.Injector)

[morigs]

@samber Hi, this issue has a lot of thumbs up. What's your opinion?

[samber]

Hey @diamondburned @morigs

I like the idea. Let's plan this feature in v2.1

[wHoIsDReAmer]

You can just put context.Context in di container. did you try that? or is this ugly?

[diamondburned]

I believe I probably tried that at one point and wasn't happy with the result. This is a year ago so I can't remember exactly why, probably should've had an Alternatives Considered section.

[edocevol]

Some scenarios do require logical switching based on the value in the ctx, and even return different provider implementations.