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

Let the user define if a message is a request or response #1506

Conversation

HeinrichAD
Copy link
Contributor

This PR is a proposal how to solve issue #1496. Let me know what you think about it!

Instead of defining that every message from the left to the right side is always a request and every message from the right to the left side is always a response, I propose to used the arrow direction from the PlantUML diagram code.

Each arrow with the arrow direction on the right (->) is a request and each arrow with the arrow direction on the left (<-) is a response.

This way the users can define themselves what is a request and what is a response.


closes #1496

result

Code
@startuml
skinparam ResponseMessageBelowArrow true
skinparam style strictuml

actor Alice as A
actor Bob as B

activate A

A -> B ++ : Request
A <-- B -- : Response

A ->> B --++ : Dispatch Task

B -> A ++ : Request
B <-- A -- : Response

deactivate B
@enduml

Instead of defining that every message from the left to the right side is always a request and every message from the right to the left side is always a response, I propose to used the arrow direction from the PlantUML diagram code.

Each arrow with the arrow direction on the right (`->`) is a request and each arrow with the arrow direction on the left (`<-`) is a response.

This way the users can define themselves what is a request and what is a response.
@arnaudroques arnaudroques merged commit e04d49a into plantuml:master Aug 1, 2023
9 checks passed
@arnaudroques
Copy link
Contributor

his PR is a proposal how to solve issue #1496. Let me know what you think about it!

Well, your correction makes sense.

We will make some tests to see if there are no regression somewhere and we will keep you informed!

Thanks for your help.

@HeinrichAD HeinrichAD deleted the enhancement/seq-response-message-below-arrow branch August 1, 2023 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sequence diagram: ResponseMessageBelowArrow only working in one direction
2 participants