Skip to content
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

Closed
gjvoosten opened this issue Oct 27, 2020 · 1 comment
Assignees
Labels

Comments

@gjvoosten
Copy link
Collaborator

Technical debt description
Not all changes in the dictionary are reflected throughout the application after reloading. E.g. AccountDeactivationWorker and ReportResource (and others) get some things from the dictionary in the constructor (only called at application start-up), or even before that like in AnetApplication::runAccountDeactivationWorker.

Proposed solution
Get dictionary entries where they are needed (as late as possible/practical).

Additional context
none

@gjvoosten gjvoosten added the debt label Oct 27, 2020
@gjvoosten gjvoosten self-assigned this Oct 27, 2020
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.
@gjvoosten
Copy link
Collaborator Author

Closed by commit d7550aa as part of #3286

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant