Handle long words in notification #135

Closed
opened 2026-05-31 08:03:20 +00:00 by maxtkc · 0 comments
Owner

Long words go off the end of the notification. For instance, moving a stop results in this notification:

 Updated stop_lat, stop_lon in stops / STOP-97cb7d7f-7f85-41e1-9fd3-308e23da2d92 

The stop id here is too long and overflows off the edge of the notification. We should use hyphen based line wrapping. While we're at it, we should revamp the notification messages so they're all consistent. This should at least include the stop name. We should synchronize this naming with the history so we don't have drift in functionality.

Long words go off the end of the notification. For instance, moving a stop results in this notification: ``` Updated stop_lat, stop_lon in stops / STOP-97cb7d7f-7f85-41e1-9fd3-308e23da2d92 ``` The stop id here is too long and overflows off the edge of the notification. We should use hyphen based line wrapping. While we're at it, we should revamp the notification messages so they're all consistent. This should at least include the stop name. We should synchronize this naming with the history so we don't have drift in functionality.
maxtkc self-assigned this 2026-05-31 08:03:20 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gtfs.zone/coloring-book#135
No description provided.