A similar issue will happen if '=' is in the stage name.
The most complete fix would be to change the plugin to have a non-ambiguous way to take the same information in, such as through a stringified json object. But then both backend and frontend would have to support both formats.
A shorter term hacky fix would be for the UI to check for special characters that the joiner does not support and error out, asking the user to rename those stages.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Import the attached pipeline
Open the TX joiner plugin
Rename the plugin label to be TX & something
Open TX and Store plugin and generate schema
After the last step UI shows an error. Once the `&` in the joiner plugin is removed things work fine.