resolves #190: add historyMaxAge
parameter
#191
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.
Resolves #190 by introducing a mechanism to clean up local storage data for TOCK message history and quick replies based on a configurable
historyMaxAge
. If the age of the last message exceeds the defined maximum age, the relevant local storage keys are removed to ensure outdated data is not retained.The
historyMaxAge
property is based on thetock_web_cookie_auth_max_age
property configurable in the backend and is intended to be set to the same value.