-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Minimum height feature for bar chart #29359
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
Minimum height feature for bar chart #29359
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 40e3863:
|
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Finalized the scaling logic |
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…inimum-height-feature-bar-chart
|
@microsoft-github-policy-service agree |
|
Commenter does not have sufficient privileges for PR 29359 in repo microsoft/fluentui |
|
@AtishayMsft , I have added the changelog as well. |
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
packages/react-charting/src/components/VerticalBarChart/VerticalBarChart.base.tsx
Show resolved
Hide resolved
packages/react-charting/src/components/VerticalBarChart/VerticalBarChart.base.tsx
Show resolved
Hide resolved
change/@fluentui-react-charting-8bdce3b1-3bbd-4a1d-8000-3cd8b50e1d0c.json
Show resolved
Hide resolved
|
@AtishayMsft Please have a look at the changes for the Vertical stacked charts |
…inimum-height-feature-bar-chart
|
@AtishayMsft Are there any more changes required in this issue? |
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
packages/react-charting/src/components/VerticalStackedBarChart/VerticalStackedBarChart.base.tsx
Outdated
Show resolved
Hide resolved
…inimum-height-feature-bar-chart
…/Shubhabrata08/fluentui into minimum-height-feature-bar-chart
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…inimum-height-feature-bar-chart
|
/azp run Fluent UI React - PR and CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp help |
Supported commands
See additional documentation. |
|
/azp list |
|
/azp run |
|
Azure Pipelines successfully started running 4 pipeline(s). |
📊 Bundle size report🤖 This report was generated against 401ff6d9af9536b24ab3c52c658127d19706e030 |
🕵 fluentuiv8 No visual regressions between this PR and main |
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 401ff6d9af9536b24ab3c52c658127d19706e030 (build) |
* master: (35 commits) bugfix(react-dialog): removes context hooks invocations from styles hook (microsoft#29396) chore(react-dialog): exports DialogSurface context types and hooks (microsoft#29397) Minimum height feature for bar chart (microsoft#29359) (feat) Breadcrumb - register items via context (microsoft#29393) fix: Consider all parents as scroll parents (microsoft#29378) Changes to enable charting on fluent docsite (microsoft#29210) bugfix: ensure TreeItem emits events properly (microsoft#29390) chore(deps): bump get-func-name from 2.0.0 to 2.0.2 (microsoft#29320) chore: migrate from getNativeElementProps to getIntrinsicElementProps (microsoft#29387) applying package updates applying package updates fix: Icon in disabled Button shouldn't change color on hover or pressed (microsoft#29342) Squish changes for rebase (microsoft#28705) fix: GroupedListV2 scrollToIndex now works correctly (microsoft#29332) Fix 27482: ProgressBar has an optional state variable (microsoft#29366) remove a11y test ux from theme designer (microsoft#29379) feat: preview release (microsoft#29377) Fixed divider in the tooltip (microsoft#29357) fix (microsoft#29376) docs: Initial documentation pass (microsoft#29372) ...


New Behavior
Related Issue(s)
Can this be a viable way to implement this? As changing props can be a contract change for the component and might be a breaking change?
Basically setting the minimum scaled height for all non-zero values to 1.
If this is a viable way, I can proceed with updating the tests.
PS: I have quite less experience in this...