-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
User Story
As a: Developer
I want to: better control the hierarchy and composition of components
Because: because it is hard er to reason about complex components that abstracts all its sub-components
Additional Context
Add any context, screenshots, designs, links, etc. about the feature request here.
- the intention here is to start building a base of elements for components, so that there is more consistency between components
- note that this should not be confused with Overrides, those are for more complex component-component compositions
Acceptance Criteria
List of conditions that mark the story as complete
- re-implement complex components that can benefit from a flat component heirarchy
- start building a sub-library for highly re-useable 'elements' (atoms) - https://varun.ca/flattening-deep-hierarchies-of-components/
Edge cases
List of edge cases to be considered when marking the story as complete
- [ ]
Technical Description (not required initially)
A technical description of the problem, this should be completed by the engineering manager/developer
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels