Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ID field with spaces and other special characters #91

Open
madhurrya opened this issue May 9, 2024 · 2 comments · Fixed by #94
Open

ID field with spaces and other special characters #91

madhurrya opened this issue May 9, 2024 · 2 comments · Fixed by #94
Assignees

Comments

@madhurrya
Copy link

In the editor for ID field of items like Errors, Signals, Escalations, Dataobjects etc. if we enter a space or some special characters like &, # etc after we save that model and load it then that item is missing. For example please see this video.
https://drive.google.com/file/d/1heEO21hpSWP_yWLfNG2yEOb9LNWWXMqc/view?usp=sharing

image

image

@jasquat
Copy link
Contributor

jasquat commented May 9, 2024

It actually gets added to the xml but then it isn't displayed when reloading the diagram. After saving the diagram again, the error is removed from the xml. In general spaces are not allowed in id's I think so maybe we should not allow special characters or spaces in it if we can.

@calexh-sar calexh-sar linked a pull request Jun 18, 2024 that will close this issue
@burnettk burnettk reopened this Jun 26, 2024
@madhurrya
Copy link
Author

  1. The Ids get trimmed for the boundary events if there is a space. But if there are special characters in the Id, the above issue is still there.

  2. For the process Id if I type with a space it shows a warning, but I can save it. Then when I open it again, the diagram is missing.
    Please see this video. https://drive.google.com/file/d/11pYgPdswafGsRHXX1QvYT8RCTk3bMq-i/view?usp=sharing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

4 participants