-
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
Add isHorizontal=true to Participant / Lane DI shapes #934
Labels
Comments
nikku
added
forgiveness
miwg
Tracks BPMN compatibility issues
modeling
enhancement
New feature or request
labels
Jan 22, 2019
1 task
ghost
assigned barmac
Jan 23, 2019
ghost
added
in progress
Currently worked on
and removed
ready
Ready to be worked on
labels
Jan 23, 2019
barmac
added a commit
that referenced
this issue
Jan 25, 2019
barmac
added a commit
that referenced
this issue
Jan 25, 2019
ghost
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Jan 25, 2019
barmac
added a commit
that referenced
this issue
Jan 30, 2019
barmac
added a commit
that referenced
this issue
Jan 30, 2019
barmac
added a commit
that referenced
this issue
Jan 31, 2019
Closed via #936 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
The
isHorizontal
attribute on participant and lane DI shapes is meta-data that helps editors to understand how these elements are laid out. Quoting from the BPMN spec (p. 373):The attribute is not necessarily required, thus this feature request falls into the forgiveness / compatibility category.
Describe the solution you'd like
We should add the attributes, as we only support horizontal modeling anyway and "fix" existing diagrams by gradually introducing the
isHorizontal=true
on newly created participant / lane DI shapesisHorizontal=true
on update participant / lane DI shapesDescribe alternatives you've considered
Additional context
Reported in camunda/camunda-modeler#1096, too.
The text was updated successfully, but these errors were encountered: