feat(cli): Add --exclude-relationships and relationship filtering #33
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.
This PR introduces relationship-level filtering and a clearer CLI for excluding edges at render time.
Closes #27
Summary
--exclude-relationships
(CSV) to the CLI to hide specific relationship types: dependency, composition, inheritance, realization. Aliases supported (dep/comp/extends/implements).Relationships
collection to encapsulate relationship storage, sorting, and filtering.RenderOptions
with explicit required flags and aRenderOptions::default()
factory.ClassDiagram::render()
viaRelationships::filter(RenderOptions)
.--only-properties-deps
and previous--exclude
(no compatibility kept as requested).Why
Details
RenderOptions
now requires 4 boolean args; useRenderOptions::default()
for defaults.ClassDiagram
now holdsRelationships
instead of an array.Examples
vendor/bin/mermaid-class-diagram generate --path src --exclude-relationships dependency,composition
vendor/bin/mermaid-class-diagram generate --path src --exclude-relationships dependency
Testing
Notes
--include-relationships
if desired for explicit whitelisting.