Why are you creating this PR? What does is solve? Include links to relevent Github issues and other resources.
Use Cases
In order for a component to be merged into the design system it must have a minimum of three separate use cases or two
plausible future buisness cases. Please include any relevant contextual information and screenshots showing these use cases or implementation discrepencies this component resolves.
1.
2.
3.
API changes
Are you making any API changes? Did you create a separate PR first to change the docs and approve the changes?
Implementation Notes
Anything that could be helpful to the reviewer. Especially if it not obvious from looking at the diffs.
Rendering and Storybook location
In order to keep design and development in-sync each component must new component must follow the folder structure below
Motivation
Why are you creating this PR? What does is solve? Include links to relevent Github issues and other resources.
Use Cases
In order for a component to be merged into the design system it must have a minimum of three separate use cases or two plausible future buisness cases. Please include any relevant contextual information and screenshots showing these use cases or implementation discrepencies this component resolves.
1.
2.
3.
API changes
Are you making any API changes? Did you create a separate PR first to change the docs and approve the changes?
Implementation Notes
Anything that could be helpful to the reviewer. Especially if it not obvious from looking at the diffs.
Rendering and Storybook location
In order to keep design and development in-sync each component must new component must follow the folder structure below
Functional Tests
You should functionally test your changes. Can you list the cases you tested?