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

Sub-component ordering issue #35

Open
akerouanton opened this issue May 29, 2019 · 3 comments
Open

Sub-component ordering issue #35

akerouanton opened this issue May 29, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@akerouanton
Copy link

Hello,

First of all, thanks for your great project.

After several attemps, it looks like sub-component ordering is not working as expected.

In the following example, the subcomponent "middlewares" should come first and "storage" subcomponent should be at the right of "middlewares". Unfortunately, there's no way to get that, even with a hidden arrow (with right indication):

node "my\nsubprocess" {
    [stdout]
}

node "my process" {
    node "middlewares" as middlewares {
        [stdout] -right-> [some processing]
    }
    node "storage" as storage {
        [some processing] -right-> [storage writer]
    }
    middlewares -[hidden]right-> storage
}

@enduml

@arnaudroques
Copy link
Contributor

@akerouanton
Copy link
Author

@arnaudroques Thanks, indeed it works properly with this directive. However, if I add bottom notes they are not placed correctly now. It's not a big deal, but still a bit surprising.

@startuml
left to right direction
node "my\nsubprocess" {
    [stdout]
}

node "my process" {
    node "middlewares" as middlewares {
        [stdout] --> [some processing]
    }
    node "storage" as storage {
        [some processing] --> [storage writer]
    }
}

note bottom of [some processing] : io.Writer
note bottom of [storage writer] : io.Writer
@enduml

gives me:

@arnaudroques
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants