broaden usage options for list-item #8587
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Builds ready [a7f288f]
Page Load Metrics (644 ± 68 ms)
|
brad-decker
force-pushed
the
refactor-list-item
branch
from
601d04a to
7027b9f
Compare
Builds ready [7027b9f]
Page Load Metrics (626 ± 54 ms)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of my work on #8564, I needed to make some changes to the list-item, and in discussion with @Gudahtt, we decided to broaden the list-item UI component to be more general purpose. This is the resulting component, with updated
.storiesto show how it is intended to be used to display transaction data.