🔧(collaboration) make the version history granularity configurable

Version grouping used a hard-coded 60s window, and its timestamps are minted server-side. We now expose COLLABORATION_VERSION_GRANULARITY_MS through /config, read it in useDocActivity. By doing so, we can control the granularity of version history with settings, it can be adjusted as needed. It will help us to test different version history granularities in our e2e tests.
2026-09-26 11:35:05 +02:00 · 2026-09-22 16:03:33 +02:00
parent daad1f380f
commit 69f84df6bb
15 changed files with 119 additions and 126 deletions
@@ -38,6 +38,7 @@ These are the environment variables you can set for the `impress-backend` contai
 | CACHES_SESSION_IGNORE_EXCEPTIONS                | Ignoring exception, behave like a missed cache. Highly recommended to set it as False when used with redis (See https://github.com/jazzband/django-redis#memcached-exceptions-behavior)   | False                                                                   |
 | CACHES_SESSION_SOCKET_CONNECT_TIMEOUT           | Timeout for the connection to be established for the session cache (In seconds)                                                                                            | 0.5                                                                     |
 | CACHES_SESSION_SOCKET_TIMEOUT                   | Timeout for read and write operations after the connection is established for the session cache (In seconds)                                                               | 1                                                                       |
+| COLLABORATION_VERSION_GRANULARITY_MS            | How coarse the document version history is, in milliseconds: edits closer together than this are shown as one version, and none spans more than this. Sent to the collaboration server as the grouping window and re-applied in the browser.   | 60000                                                              |
 | COLLABORATION_WS_INACTIVITY_TIMEOUT             | Timeout (in seconds) after which the user is considered inactive when there is no activity. The WebSocket is closed after this inactivity period. `None` means disabled.   | None                                                                    |
 | COLLABORATION_WS_URL                            | Collaboration websocket url                                                                                                                                                |                                                                         |
 | CONVERSION_API_CONTENT_FIELD                    | Conversion api content field                                                                                                                                               | content                                                                 |