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

PlantUml components grouping support #213

Open
decarufe opened this issue Jun 28, 2023 · 0 comments
Open

PlantUml components grouping support #213

decarufe opened this issue Jun 28, 2023 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@decarufe
Copy link

To simpify diagram it would be nice to support all grouping keywords

  • package
  • node
  • folder
  • frame
  • cloud
  • database

For example in the folling diagram I commented all direct component dependecies and use grouping dependencies instead.

@startuml Architecture Diagram
package ApplicationGroup {
  [Application] <<TheServiceName.WebApi.*>>
}

package DomainGroup {
  [Domain] <<TheServiceName.Domain.*>>
  [Infrastructure] <<TheServiceName.Infra.*>>
  [Databases] <<TheServiceName.Database.*>>
}

package AbstractionsGroup {
  [Abstractions] <<TheServiceName.Abstraction.*>>
}

' These components dependencies are inferred by the package dependencies
' Application --> Databases
' Application --> Infrastructure
' Application --> Domain
ApplicationGroup --> DomainGroup


' These components dependencies are inferred by the package dependencies
' Databases --> Abstractions
' Infrastructure --> Abstractions
' Domain --> Abstractions
Infrastructure -> Domain
DomainGroup --> AbstractionsGroup

' Infer dependencies: Because ApplicationGroup depends on DomainGroup, and DomainGroup depends on AbstractionsGroup, then ApplicationGroup depends on AbstractionsGroup
' Application --> Abstractions
' ApplicationGroup --> AbstractionsGroup


@enduml

I expect:

  • All seteretypes (<<...>>) defined in a group to be considered in that group
  • Dependency validation can be defined between group definition
  • Cascading definition to be validated (i.e.: A --> B and B --> C implies A --> C)
@alexanderlinne alexanderlinne added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants