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
Customized stories - 3740 #3863
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for picking this up.
The story you found is based on an old example, we initially just copied it. could you please also clean it up? Given that in the API section we want to document the API of each component, I believe exposing the data
in the Args is misleading.
Please adapt the story so that the control does not include the data.
d0040fa
to
b5d1e39
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good start! I wish we could type some more of the props but I think thats more an issue with the nature of Customized
than an issue here.
Thanks!
|
||
## Parent Component | ||
|
||
The Customized can be used within: `<LineChart />`, `<BarChart />`, `<ComposedChart />`, `<AreaChart />`, `<PieChart />`, `<RadarChart />`, `<RadialBarChart />`, `<ScatterChart />` or `<FunnelChart />`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, wording: "The" here can be omitted
<!--- Provide a general summary of your changes in the Title above --> ## Description I think we already have Customized story but on wrong path, So I updated the path for that. <!--- Describe your changes in detail --> ## Related Issue Issue: [3740](recharts#3740) <!--- This project only accepts pull requests related to open issues --> <!--- If suggesting a new feature or change, please discuss it in an issue first --> <!--- If fixing a bug, there should be an issue describing it with steps to reproduce --> <!--- Please link to the issue here: --> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> ## How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [x] I have added a storybook story or extended an existing story to show my changes - [x] All new and existing tests passed. Co-authored-by: Shashang Bhagat <shashangbhagat@gamil.com>
Description
I think we already have Customized story but on wrong path, So I updated the path for that.
Related Issue
Issue: 3740
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: