-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make sure all changes in the dictionary are reflected everywhere after reloading #3268
Labels
Comments
gjvoosten
added a commit
that referenced
this issue
Oct 29, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 4, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 5, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 9, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 10, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 11, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 12, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 12, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 16, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 16, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 17, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 18, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 18, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
gjvoosten
added a commit
that referenced
this issue
Nov 18, 2020
With the exception of the AccountDeactivationWorker schedule, changes in the dictionary are now properly reflected after a reload.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Technical debt description
Not all changes in the dictionary are reflected throughout the application after reloading. E.g.
AccountDeactivationWorker
andReportResource
(and others) get some things from the dictionary in the constructor (only called at application start-up), or even before that like inAnetApplication::runAccountDeactivationWorker
.Proposed solution
Get dictionary entries where they are needed (as late as possible/practical).
Additional context
none
The text was updated successfully, but these errors were encountered: