There is a feature of destroying participant/actor objects, when designing sequence diagrams in mermaid. It's defined in mermaid, that destroy action should associate with a destroying message after its declaration.
However, if you leave the contents of the destroying message empty; then the previous message arrow will point not to the lifeline of the participant/actor object being destroyed, but to the participant/actor object itself:
[Picture1]
Furthermore, if the previous message arrow was associated with create action (which is pretty unrealistic, but still...), then it causes even more chaos:
[Picture2]
On the other hand, if you fill contents of the destroying message:
in case of preceeding message being associated to a create action, rendered participant/actor objects will not overlap;
[Picture3]
in other cases, rendered message arrow will point to the lifeline of participant/actor object, being destroyed.
[Picture4]
Steps to reproduce
Code to recreate the pictures provided in the description:
[Picture1]:
Description
There is a feature of destroying
participant
/actor
objects, when designing sequence diagrams in mermaid. It's defined in mermaid, thatdestroy
action should associate with a destroying message after its declaration.However, if you leave the contents of the destroying message empty; then the previous message arrow will point not to the lifeline of the
Furthermore, if the previous message arrow was associated with ![image](https://github.com/mermaid-js/mermaid/assets/60223738/c4fdc946-a6fc-4817-88cd-ef531c765a38)
participant
/actor
object being destroyed, but to theparticipant
/actor
object itself: [Picture1]create
action (which is pretty unrealistic, but still...), then it causes even more chaos: [Picture2]On the other hand, if you fill contents of the destroying message:
create
action, renderedparticipant
/actor
objects will not overlap; [Picture3]participant
/actor
object, being destroyed. [Picture4]Steps to reproduce
Code to recreate the pictures provided in the description: [Picture1]:
[Picture2]:
[Picture3]:
[Picture4]:
Screenshots
No response
Code Sample
No response
Setup
Suggested Solutions
No response
Additional Context
No response