[Bug] Component Editor stops working when component name contains special characters like parenthesis

[Ark-kun]

[camielvs]

I am unable to reproduce this.

I don't think Task Names can support special characters - but you can use the display_name annotation for this

[maxy-shpfy]

🤖 Auto-triage assigned priority P2

The issue involves a bug where the Component Editor stops working when special characters are used in component names. This is a user-reported bug affecting functionality, but it is not critical as there is a workaround using the display_name annotation. It does not render the application unusable, hence not a P0 or P1.

Key factors:
• user-reported bug
• workaround available
• does not break entire application

🔧 P2 Priority: Feature cleanup/improvement to be planned and completed within normal cycle.

This priority was determined by AI analysis with 90% confidence.

[Ark-kun]

I am unable to reproduce this.

1. Start creating new Bash component.
2. Type "[" or "(" in the middle of the name:

name: "Filter [text using shell and grep"

Preview at the right fails immediately.

I don't think Task Names can support special characters

Task IDs can be anything. So are component names.

I've seen many components with names like "[Official] Whatever" in the wild.

To fix the bug, the code that uses regexp should just quote the string before using it in regexp.
See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/escape (although it's a bit new)