8000 fix: lane statement handler of puml by J0HN50N133 · Pull Request #169 · any-block/any-block · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix: lane statement handler of puml #169

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 28, 2025
Merged

fix: lane statement handler of puml #169

merged 1 commit into from
May 28, 2025

Conversation

J0HN50N133
Copy link
Contributor

No description provided.

8000
@LincZero
Copy link
Member
LincZero commented May 27, 2025 •
edited
Loading

过两天再看，不可抗力因素这两天没电脑用

I'll check in a couple of days. Due to force majeure, I won't be able to use the computer these two days

@LincZero LincZero merged commit a598094 into any-block:main May 28, 2025
4 checks passed
@LincZero LincZero self-assigned this Jun 3, 2025
@LincZero
Copy link
Member
LincZero commented Jun 3, 2025 •
edited
Loading

感觉不对，这样的话需要强制一开始就加泳道图的声明。否则就会出错

但往往不一定需要用到这个，否则徒增语法复杂性。之前没仔细检查，demo挂了

我先Revert了

image

@LincZero LincZero mentioned this pull request Jun 3, 2025
Merged
@J0HN50N133
Copy link
Contributor Author
J0HN50N133 commented Jun 3, 2025 •
edited
Loading

@LincZero 泳道实际上并不需要声明，只是 start 不能出现在第一个泳道之前。
以下面这个 puml 官方的代码片段为例：

@startuml
|Swimlane1|
start
:foo1;
|#AntiqueWhite|Swimlane2|
:foo2;
:foo3;
|Swimlane1|
:foo4;
|Swimlane2|
:foo5;
stop
@enduml

这块儿之前的实现有问题就是因为对这里的文档理解有误，认为所有泳道都要在最前面进行声明，反而导致出现了问题。demo 你把 start 挪到 lane 后面就行了。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@LincZero LincZero LincZero approved these changes

Assignees

@LincZero LincZero

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@J0HN50N133 @LincZero
0