Cards are increasingly common in the application. Messages already incorporate them, and Documents will too (see issue #606 ). We should implement a reusable Card component.
Rationale:
Simplifies the use of cards throughout the application by providing reusable code.
Proposed Changes:
Create an expandable/collapsible card component
Props should tentatively include a header, type, and data to display
Parse over data, and populate the card (default and expanded)
Replace cards in application with new component
Possible Drawbacks:
Card types may differ enough to warrant separate components
Describe the Current Behavior/Feature:
Cards are increasingly common in the application. Messages already incorporate them, and Documents will too (see issue #606 ). We should implement a reusable Card component.
Rationale:
Simplifies the use of cards throughout the application by providing reusable code.
Proposed Changes:
Possible Drawbacks:
Alternatives Considered:
N/A
Additional Context:
This is part of an ongoing greater refactoring