[5.8] Bug fix related to extra calls to resolving callbacks (The Other Way) #27059
Conversation
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
imanghafoori1
changed the title
imanghafoori1
force-pushed
the
fix_extra_calls_other_way
branch
from
df0e44b
to
5589461
Compare
+ bug fix related to multiple calls to "resolving" and "afterResolving" callbacks
imanghafoori1
force-pushed
the
fix_extra_calls_other_way
branch
from
5589461
to
8cdd1f2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an other way of fixing the issue of "multiple calls to resolving callback" which came to my mind while I was under the shower today.🚿 🛀
Compared to the solution in: #27014 ,it requires a less code and is more understandable and logical.
Plus, it adds a new feature to the IOC container for resolving an object silently. (Which can suppress the resolving callbacks to be fired.)