Telemetry Viewer screen names with spaces

[jmthomas]

We shouldn't allow spacing in any screen names because ultimately that creates filenames with spaces. As part of this we should allow people to rename screens.

[crawlchat]

Thanks for raising this issue! This is a well-scoped and actionable request. Here's a summary of the current state and what needs to change:

Current State

Looking at NewScreenDialog.vue, the current screen name input:

• Lowercases the name when auto-populated from a packet (value.toLowerCase())
• Checks for duplicate names
• But does NOT validate against spaces in the name

What Needs to Be Done

There are two separate work items here:

1. Disallow spaces in screen names — The v-text-field for screen name input in NewScreenDialog.vue needs a validation rule to reject names containing spaces. Something like:

   noSpaces: (value) => !/\s/.test(value) || 'Screen name cannot contain spaces.'

   And ideally strip/replace spaces on input (e.g., replace spaces with underscores automatically).

2. Allow renaming of existing screens — There is currently no "rename screen" functionality. This would require:

   • A rename option in the screen title bar (e.g., alongside the existing pencil/edit icon)
   • A backend call to rename the screen file (delete old, save new)
   • Updating the screen list in TlmViewer.vue after rename

Could you also clarify a couple of things to help prioritize:

• Should spaces be replaced automatically (e.g., my screen → my_screen), or should we block the input entirely with an error?
• For renaming, should it be accessible from the screen title bar, the Edit Screen dialog, or both?

[EmilyRagan]

Re: crawl chat's suggestion to "delete old, save new" in order to rename the screen file
Since we have started talking about maintaining history on scripts, if we want to consider maintaining history on other files, like screens, maybe we want to figure out a way to rename that doesn't disassociate the history from before the rename happened