support optional component keyword in PlantUML diagram rules
#1223
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
|
PR should be rebased after the #1184 merge so it will contain only a single commit |
It is valid PlantUML syntax to prepend the `component` keyword to a component declaration, e.g. ``` component [MyComponent] <<..mycmp..>> ``` Since it doesn't create a big overhead to support this as an optional part of the component declaration, we can add it to make it easier for users that distinguish their components from other types of objects like databases. Signed-off-by: Tomasz Fijalkowski <3066563+tfij@users.noreply.github.com>
codecholeric
force-pushed
the
plantuml-support-optional-component-keyword
branch
from
39190ba
to
2ec2db2
Compare
codecholeric
changed the title
component keyword in PlantUML diagram rules
codecholeric
approved these changes
Apr 10, 2024
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.
It is valid PlantUML syntax to prepend the
componentkeyword to a componentdeclaration, e.g.
Since it doesn't create a big overhead to support this as an optional part
of the component declaration, we can add it to make it easier for users
that distinguish their components from other types of objects like databases.