-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
#110 Support properties and node description #111
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on forced relations
…-line-breaks-of-type-labels
…-line-breaks-of-type-labels (2 - update link with updated C4_Deployment Diagram Sample)
…om tags/stereotypes support; dynamic legend supports custom colors, border and shadow; dynamic legend displays (only) used elements, tags/stereotypes. New added macros: SHOW_DYNAMIC_LEGEND(), AddTagSupport(), UpdateSkinparamsAndLegendEntry(), elements macros are extended with $tags="..."
…om tags/stereotypes support; ... (2 - update macros docu with added $tags="...")
…line argument -DRELATIVE_INCLUDE="." Update github workflow that local files are used
…line argument -DRELATIVE_INCLUDE="." (2 - fix !if)
…line argument -DRELATIVE_INCLUDE="." Update github workflow that local files are used
(Deployment_)Node() supports description, sprite and left/right alignment via Node_L()/Node_R() * Element properties can be defined via SetPropertyHeader(), WithoutPropertyHeader() and AddProperty()
Potherca
approved these changes
Feb 1, 2021
These are some insane PlantUML skills 🤯 |
adrianvlupu
approved these changes
Feb 6, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no doubt this will turn to hell when something changes in the PlantUML preprocessor but I can't help myself
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
That I can create document a detailed documentation too. I added following extensions.
(Deployment_)Node elements are extended with following macros:
Properties can be added with following macros:
and can be used like below
A preview of the PR can be found in my extended branch
The extensions are compatible with the .dotnet structurizr model and enables a detailed deployment diagram too.
BR Helmut