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

Illegal IDs may be entered via properties panel #1623

Closed
3 tasks
Assignees
Labels
bug Something isn't working
Milestone

Comments

@nikku
Copy link
Member

nikku commented Dec 3, 2019

Describe the Bug

Starting with v3.2.0 we enforce that XML IDs generated by the application are valid QNames. as #1622 indicates users are still able to input now illegal IDs, i.e. ${FOO}. Saving the diagram and re-opening it in the modeler fails the import.

Steps to Reproduce

  1. open process
  2. using our properties panel controls change any ID to ${FOO}
  3. save diagram
  4. re-open diagram
  5. see that import blows up

Expected Behavior

  • Valid IDs are enforced in all property panel controls that allow users to edit IDs
  • Illegal IDs may not be saved by the user

Environment

  • OS: Any
  • Camunda Modeler Version: v3.2.0, ..., v3.5.0

Tasks

  • Fixed in properties panels
  • Released fixes
  • Integrated in Camunda Modeler
@nikku nikku added the bug Something isn't working label Dec 3, 2019
@nikku nikku added the ready Ready to be worked on label Dec 3, 2019
@nikku nikku added this to the M33 milestone Dec 3, 2019
@oguzeroglu oguzeroglu self-assigned this Dec 9, 2019
@oguzeroglu oguzeroglu added in progress Currently worked on and removed ready Ready to be worked on labels Dec 9, 2019 — with bpmn-io-tasks
@oguzeroglu
Copy link
Contributor

oguzeroglu commented Dec 9, 2019

Valid IDs are enforced in all places where we allow users to edit IDs

Does this concern the XML edit as well @nikku?

@nikku
Copy link
Member Author

nikku commented Dec 9, 2019

You mean the XML editor? No. If people enter invalid IDs into the XML view the problem will be caught on import and properly indicated.

Adding validation on the XML view would be another related feature request.

@oguzeroglu
Copy link
Contributor

oguzeroglu commented Dec 9, 2019

For reference: The problem seems to be here as after this operation ${FOO} becomes FOO so it passes the QName regex test.

@nikku
Copy link
Member Author

nikku commented Dec 9, 2019

Yes. This was intentional in the past but is not desired anymore.

oguzeroglu pushed a commit to bpmn-io/bpmn-js-properties-panel that referenced this issue Dec 10, 2019
oguzeroglu pushed a commit to bpmn-io/dmn-js-properties-panel that referenced this issue Dec 10, 2019
oguzeroglu pushed a commit to bpmn-io/cmmn-js-properties-panel that referenced this issue Dec 10, 2019
@bpmn-io-tasks bpmn-io-tasks bot removed the in progress Currently worked on label Dec 10, 2019
nikku pushed a commit to bpmn-io/dmn-js-properties-panel that referenced this issue Dec 10, 2019
nikku pushed a commit to bpmn-io/bpmn-js-properties-panel that referenced this issue Dec 10, 2019
nikku pushed a commit to bpmn-io/cmmn-js-properties-panel that referenced this issue Dec 10, 2019
@nikku nikku reopened this Dec 10, 2019
@nikku
Copy link
Member Author

nikku commented Dec 10, 2019

Needs release of fixes in all libraries and integration into Camunda Modeler.

@nikku nikku added the fixed upstream Requires integration of upstream change label Dec 10, 2019
@nikku
Copy link
Member Author

nikku commented Dec 11, 2019

Closed via f906e14.

@nikku nikku closed this as completed Dec 11, 2019
@bpmn-io-tasks bpmn-io-tasks bot removed the fixed upstream Requires integration of upstream change label Dec 11, 2019
@nikku nikku mentioned this issue Jan 22, 2020
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants