feat(fx): add Transient provider option for non-cached constructors #1280
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, fx.Provide() always registers constructors as singletons, meaning their results are reused for the lifetime of the app.
In some cases, it’s desirable to have fresh instances, for example:
Introduces a new fx.Transient() helper that allows constructors to be invoked each time their dependency is requested, rather than once at application start.
This enables transient or per-request dependency lifetimes similar to scoped services in other DI systems. The Transient wrapper registers a factory function that produces a new instance on each call.
Includes unit tests verifying:
Backward compatibility
No breaking changes — existing Fx applications continue to behave identically.
The new feature is purely additive.
Documentation and usage examples will be added in a follow-up PR after this change is approved.