bluerobotics / bluerobotics/cockpit

frontend: alerter: improve long message support

Open
#2,283 0 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue ui ux widget-specific
Dominant language
TypeScript
Stars
198
Forks
63
Avg merge
2d 7h
Merged PRs (30d)
57

Description

### Current behaviour

1. #1083 added truncation with ellipses, but that means long messages can only be viewed as tooltips.
2. MAVLink [`STATUSTEXT`](https://mavlink.io/en/messages/common.html#STATUSTEXT) messages (the source of most of our alerter alerts) are currently sent immediately to the alerter, even if only partially formed

### Expected or desired behaviour

1. Ideally long messages would either wrap over multiple lines, or at least support some kind of auto-scrolling behaviour to allow reading them when they're visible (like in our [ScrollingText](https://github.com/bluerobotics/cockpit/blob/master/src/components/ScrollingText.vue) component).
2. The message definition has a limited character length, but there's a specified splitting and sequence re-combination mechanism, to allow sending longer messages, and it would be good if we could support that properly

### Prerequisites

- [x] I have checked to make sure that a similar request has not already been filed or fixed.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with src/components/ScrollingText.vue to review the existing scrolling behavior, then locate the alerter code that receives MAVLink STATUSTEXT messages. Define how split messages are recombined and how long alerts are displayed. Done means long messages can be read and segmented STATUSTEXT messages appear as one complete alert.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.