-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Broken connection layout when reconnecting to create a loop #1121
Comments
pinussilvestrus
added
in progress
Currently worked on
and removed
ready
Ready to be worked on
labels
Aug 6, 2019
— with
bpmn-io-tasks
pinussilvestrus
added
ready
Ready to be worked on
and removed
in progress
Currently worked on
labels
Aug 7, 2019
— with
bpmn-io-tasks
philippfromme
added a commit
that referenced
this issue
Aug 19, 2019
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
ready
Ready to be worked on
labels
Aug 19, 2019
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Aug 19, 2019
philippfromme
added
in progress
Currently worked on
and removed
needs review
Review pending
labels
Aug 20, 2019
— with
bpmn-io-tasks
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Aug 20, 2019
philippfromme
added a commit
that referenced
this issue
Aug 20, 2019
philippfromme
added a commit
that referenced
this issue
Aug 20, 2019
Closed via 6aaf816 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
This applies only to connections with more than 2 waypoints. When reconnecting start/end to form a loop, the connection is laid out incorrectly. It applies to both old and current bpmn-js versions, although the way the connection is laid out is different.
bpmn-js@<=3
bpmn-js@4.0.0-beta.11
Steps to Reproduce
Steps to reproduce the behavior:
Expected Behavior
Layout as if the loop were created from scratch.
Environment
Please complete the following information:
bpmn-js@4.0.0-beta.11
The text was updated successfully, but these errors were encountered: