When the diagram is big and not all participants can be seen (either moved out vertically or horizontally), we should provide a mechanism to show the participants when user's mouse is hovering on a message.

Here are a few options:

1. show participant labels at the bottom.
2. Stick the participant labels at the top when scrolling.
3. Show From/To as tooltips of a message.
4. Support compact mode.

Tailwindcss leaks to global. When we import the vue-sequence.css, it applies !important to all tailwind css classes which override hosting page's css.

Scope

Viewing Only

Out of scope

Persisting toggles

Context

When viewing a Sequence Diagram, sometimes, some details (be it messages, fragments or branches) become distractions. Users may want to temporarily hide it.

Design

The meaning of "hide" is important. We need to carefully design the hidden section so it does not continue distracting users' attention but still providing some indicator (and maybe some information) on what is going on there. A few example's must be provided.

Branches

Messages

Fragments

Related Issues

Feature request: toggle branch of code

For example

// A user or an application who/which owns a protected resource on the _Resource Server_
"Resource Owner (user)"
OR

Client // The client or third party application requests access to the resources

Should be rendered as:

An example with tailwind component:

<div class="p-20">
  <div class="mt-60">
    <div class="group relative inline-block rounded-lg text-[0.8125rem] leading-5 ring-2 ring-indigo-600 duration-300 hover:bg-slate-50 hover:text-red-500">
      <!-- Tooltip text here -->
      <span class="absolute min-w-[200px] rounded-lg -translate-y-full bg-gray-700 px-2 py-1 text-center text-sm text-white group-hover:flex">A user or an application who/which owns a protected resource on the _Resource Server_</span>
      <div class="p-4 font-medium text-slate-900">Resource</div>
    </div>
  </div>
</div>

const order = await OrderRepository.createOrder()

When users use the above line, const is parsed as a participant; await is parsed as a method. For those very common keywords, we should at least allow them.

We should send them to a TYPE channel or ASYNC_CHANNEL (or METHOD_MODIFIER?).

The error message printed in console is not helpful for the below code:

new A() {
    C.m() {    
}

Error: line 1:8 mismatched input '{' expecting

For this syntax: === divider should allow space ===.

new A(x) {
  if (condition){
    B.method()
  }
}

It also has impact on other fragment components:

1. Loop
2. Par
3. Opt
4. TCF (try/catch/finally)

It does not have impact on:

1. simple message (sync and async)
2. creation
3. return/reply

This is a useful feature that applies to most of our products if not all.

tsayen/dom-to-image#310 (comment)

• xxx
• yyy

[]yyy
[x]yyy

Discussed in #392

// [red]
A.method()

Should render the message in red.

We can do a lot more with this syntax.
tailwind css and shortcuts can be used:

1. text-red-900
2. text-red
3. red
4. font-bold
5. bold

plus no reset to 100% when clicking the middle.

This is an EPIC. It has a lot of subtasks. Make sure that the documentation is accessible from where it is needed (Tooltip footer is an option)