-
Notifications
You must be signed in to change notification settings - Fork 458
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
Add InvalidateCache to DependencyInjectionNamingSubsystem #556
Add InvalidateCache to DependencyInjectionNamingSubsystem #556
Conversation
protected override void InvalidateCache() | ||
{ | ||
handlerListsRegistrationOrderByTypeCache.Clear(); | ||
handlerListsPriorityOrderByTypeCache.Clear(); | ||
base.InvalidateCache(); | ||
} |
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.
Can you add a unit test to show what this is fixing and so we don't get that defect back.
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.
Yes, but not until next week.
Good point, Thabks
…DecoratorsNotWorking
Hi @jonorossi. Tests added. Also cleaned up unused collection. I have changed the handlerListsByTypeCache to be protected, so the overriding GetHandler uses the same collection as the base, And hence the InvalidateCache in the base does not need to be overridden. |
Thanks @twenzel ypu are welcome to push to my fork if you want. |
Hi @twenzel I don't think the fork is locked is it? Other have been able to push to it. Is you try? |
@jonorossi if you have time, looks like we are ready to complete :-) |
Add InvalidateCache to DependencyInjectionNamingSubsystem when services are registering
#552