refactor!(git): default to useMaxWidth
true
#5723
Merged
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.
📑 Summary
Change the default value for
gitGraphs.useMaxWidth
totrue
, as all mermaid diagrams default touseMaxWidth
astrue
, with the exception of Sankey diagrams and git graphs.The documentation currently says it defaults to
true
, so changing this matches the documentation. See:mermaid/packages/mermaid/src/schemas/config.schema.yaml
Lines 306 to 312 in d4d7ca7
BREAKING CHANGE: Changes the default value of
useMaxWidth
for gitgraphs totrue
. This is technically a breaking change, but considering that most of the other diagrams default totrue
, I think this is unlikely to impact anybody.However, if anybody does want the old behavior, they can always explicitly set
{ gitGraph: { useMaxWidth: false } }
.📏 Design Decisions
N/A
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.develop
branch