mirror of
https://github.com/octoleo/plantuml.git
synced 2024-12-22 10:59:01 +00:00
define -> arrows as request and <- as response
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.
This commit is contained in:
parent
49115dfc7d
commit
9fe1686e40
@ -185,7 +185,7 @@ public class ComponentRoseArrow extends AbstractComponentRoseArrow {
|
|||||||
}
|
}
|
||||||
|
|
||||||
private boolean isBelowForResponse() {
|
private boolean isBelowForResponse() {
|
||||||
return belowForResponse && getDirection2() == ArrowDirection.RIGHT_TO_LEFT_REVERSE;
|
return belowForResponse && getArrowConfiguration().isReverseDefine();
|
||||||
}
|
}
|
||||||
|
|
||||||
private void drawDressing1(UGraphic ug, ArrowDressing dressing, ArrowDecoration decoration, double lenFull) {
|
private void drawDressing1(UGraphic ug, ArrowDressing dressing, ArrowDecoration decoration, double lenFull) {
|
||||||
|
Loading…
Reference in New Issue
Block a user