Skip to content

resolves #190: add historyMaxAge parameter #191

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Fabilin
Copy link
Member

@Fabilin Fabilin commented Jun 23, 2025

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 the tock_web_cookie_auth_max_age property configurable in the backend and is intended to be set to the same value.

Copy link
Contributor

@kbvi kbvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might have put the + of lastMessageTime in its definition rather than its use (so something like +(windows... ?? 0) ), in case we need to use it later, as a uniquely typed variable...
But it's ok

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

Successfully merging this pull request may close these issues.

Message history should get cleared eventually
2 participants