[ctw-joao-luis]

User-Facing Changes

Fixed an alert spam issue in the WebSocket player where high message frequency warnings were triggered repeatedly. The alert now fires only once per connection session.

This fixes #951

Description

The FoxgloveWebSocketPlayer was not tracking whether a high-frequency topic had already been detected, causing the alert to be re-evaluated and re-added on every incoming message. This PR fixes that and also refactors the shared high-frequency detection utility to be cleaner and usable by both players.

Changes:

• Added ishighFrequencyMessage class field (reset on reconnection in the "open" handler) to ensure isTopicHighFrequency is only called until a high-frequency topic is detected. The alert is now added inline, removing the need for the checkForHighFrequencyTopics wrapper.

• isTopicHighFrequency: removed unused alerts, connectionType, startTime, and endTime parameters. The function now takes only { topicStats, topic, duration }, making it usable directly from both FoxgloveWebSocketPlayer and IterablePlayer without extra coupling;

• helpers.ts: Deleted checkForHighFrequencyTopics wrapper function;

• types.ts: Deleted CheckForHighFrequencyTopics type and its orphaned imports;

• IterablePlayer: Updated call site to the new isTopicHighFrequency signature;

• Tests updated across isTopicHighFrequency.test.ts and helpers.test.ts.

How to test it

Created this repo that can be used to test it: https://github.com/ctw-joao-luis/lichtblick-high-frequency-ws

Checklist

• The web version was tested and it is running ok
• The desktop version was tested and it is running ok
• This change is covered by unit tests
• Files constants.ts, types.ts and *.style.ts have been checked and relevant code snippets have been relocated

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
80.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud