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

refactor!(git): default to useMaxWidth true #5723

Merged

Conversation

aloisklink
Copy link
Member

@aloisklink aloisklink commented Aug 20, 2024

📑 Summary

Change the default value for gitGraphs.useMaxWidth to true, as all mermaid diagrams default to useMaxWidth as true, with the exception of Sankey diagrams and git graphs.

The documentation currently says it defaults to true, so changing this matches the documentation. See:

useMaxWidth:
description: |
When this flag is set to `true`, the height and width is set to 100%
and is then scaled with the available space.
If set to `false`, the absolute space required is used.
type: boolean
default: true

BREAKING CHANGE: Changes the default value of useMaxWidth for gitgraphs to true. This is technically a breaking change, but considering that most of the other diagrams default to true, 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

All other diagrams (with the exception of Sankey) default to `true`.

BREAKING CHANGE: Change the default value of `useMaxWidth` for gitgraphs
                 to `true`.
@aloisklink aloisklink added Type: Other Not an enhancement or a bug Graph: Git Breaking Change Breaking change labels Aug 20, 2024
Copy link

netlify bot commented Aug 20, 2024

Deploy Preview for mermaid-js ready!

Name Link
🔨 Latest commit 6b5286e
🔍 Latest deploy log https://app.netlify.com/sites/mermaid-js/deploys/66c469d203851b0008ec7407
😎 Deploy Preview https://deploy-preview-5723--mermaid-js.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot added the Type: Bug / Error Something isn't working or is incorrect label Aug 20, 2024
Copy link

codecov bot commented Aug 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 5.21%. Comparing base (04c29e2) to head (6b5286e).
Report is 18 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           develop   #5723      +/-   ##
==========================================
- Coverage     5.22%   5.21%   -0.02%     
==========================================
  Files          323     323              
  Lines        46212   46205       -7     
  Branches       537     537              
==========================================
- Hits          2415    2408       -7     
  Misses       43797   43797              
Flag Coverage Δ
unit 5.21% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
packages/mermaid/src/defaultConfig.ts 45.78% <ø> (-1.36%) ⬇️

Copy link

argos-ci bot commented Aug 20, 2024

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ⚠️ Changes detected (Review) 84 changed Aug 20, 2024, 10:15 AM

@knsv knsv added this pull request to the merge queue Aug 20, 2024
@knsv knsv removed this pull request from the merge queue due to a manual request Aug 20, 2024
@knsv knsv merged commit a48d970 into mermaid-js:develop Aug 20, 2024
19 of 20 checks passed
@aloisklink aloisklink deleted the fix/default-gitGraph-useMaxWidth-to-true branch August 20, 2024 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change Breaking change Graph: Git Type: Bug / Error Something isn't working or is incorrect Type: Other Not an enhancement or a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants