-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix decorator not being applied to transient dependencies #941
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -81,23 +81,32 @@ func (o moduleOption) apply(mod *module) { | |
type module struct { | ||
parent *module | ||
name string | ||
scope *dig.Scope | ||
scope scope | ||
provides []provide | ||
invokes []invoke | ||
decorators []decorator | ||
modules []*module | ||
app *App | ||
} | ||
|
||
// scope is a private wrapper interface for dig.Container and dig.Scope. | ||
// We can consider moving this into Fx using type constraints after Go 1.20 | ||
// is released and 1.17 is deprecated. | ||
type scope interface { | ||
Decorate(f interface{}, opts ...dig.DecorateOption) error | ||
Invoke(f interface{}, opts ...dig.InvokeOption) error | ||
Provide(f interface{}, opts ...dig.ProvideOption) error | ||
Scope(name string, opts ...dig.ScopeOption) *dig.Scope | ||
String() string | ||
} | ||
|
||
// builds the Scopes using the App's Container. Note that this happens | ||
// after applyModules' are called because the App's Container needs to | ||
// be built for any Scopes to be initialized, and applys' should be called | ||
// before the Container can get initialized. | ||
func (m *module) build(app *App, root *dig.Container) { | ||
if m.parent == nil { | ||
m.scope = root.Scope(m.name) | ||
// TODO: Once fx.Decorate is in-place, | ||
// use the root container instead of subscope. | ||
Comment on lines
-99
to
-100
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. heh |
||
m.scope = root | ||
} else { | ||
parentScope := m.parent.scope | ||
m.scope = parentScope.Scope(m.name) | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test would pass even if none of the functions executed. What guarantees the assertions on 337 and 344 are called?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Invokes are guaranteed to run (and the fact that it ran is guaranteed by
fx.RequireStart().RequireStop()
- if any Invokes fail to run, that fails the test). Invoke running successfully means assertion in line 344 are called.And yes, line 337 in itself does not guarantee the execution, but the assertion in line 344 means both constructors
Provide
d here ran successfully.