-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Charting: Vertical stacked bar chart minor changes including uncaught type error issue fix. #15447
Charting: Vertical stacked bar chart minor changes including uncaught type error issue fix. #15447
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 3cc6329:
|
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: c92c7c4caa7b3f97fc1b7198ec603bd6317ac851 (build) |
@dzearing Why is the "Charting" label no longer applied automatically? |
@jameelakowsar I will test these changes against our code and let know what works or still doesn't. |
@ecraig12345 I think the answer to @mbest question above is that the bot is perhaps looking only at target=master PRs? But i'm not sure. |
Yeah it looks like the bot only considers master PRs for path-based labeling, and I don't see an option to consider other branches unfortunately. |
Oh actually, I take that back. The way that the configuration works for this feature is a bit weird, and I think we need to update it to ignore changes to |
I've verified that this fixes the following regressions:
There are still these issues:
|
In RTL mode, the right margin isn't handled correctly. Comparing the Here's the same chart before the changes in #15061 |
What meant by 'zero-value' data? |
@mbest , If all good, I will make this PR to open. Confirm your status. |
packages/charting/src/components/CommonComponents/CartesianChart.types.ts
Outdated
Show resolved
Hide resolved
...act-examples/src/charting/VerticalStackedBarChart/VerticalStackedBarChart.Styled.Example.tsx
Outdated
Show resolved
Hide resolved
packages/charting/src/components/CommonComponents/CartesianChart.base.tsx
Outdated
Show resolved
Hide resolved
Before your "refactor" I had added this line to filter our zero-value data:
I see from looking through the
which you changed back to (and moved back into the loop even though it doesn't need to be there):
You also undid the normalization of the props that are passed to the callout handlers. You also undid the code that makes sure that |
🎉 Handy links: |
🎉 Handy links: |
…ade minor edits to margins (microsoft#15699) Cherry-pick of microsoft#15447.
Pull request checklist
$ yarn change
Description of changes
Vertical stacked bar chart.
Note: As Cartesian component consumed by other charts, Due to small change in cartesian, cross checked all other charts and added screenshots.
Focus areas to test
Vertical stacked bar chart
Vertical bar chart
Area chart
Line chart
After fix
Vertical stacked bar chart
Vertical stacked bar chart with RTL
Vertical bar chart
Vertical bar chart with RTL
No margins given - It can take default values
left:40, right: 20
Area chart
Area chart with RTL
Line chart
Line chart with RTL
Test link: http://fabricweb.z5.web.core.windows.net/pr-deploy-site/refs/pull/15447/merge/charting/dist/index.html#/examples/VerticalStackedBarChart