-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[PM-21882] Lit Components Cleanup #14872
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
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.
The inferred diff here is a little weird; this is actually a removal of the cipher-item story and a rename of the item-row story (and it's components)
|
Codecov ReportAttention: Patch coverage is
โ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #14872 +/- ##
=======================================
Coverage 36.42% 36.42%
=======================================
Files 3212 3207 -5
Lines 93280 93247 -33
Branches 16840 16840
=======================================
- Hits 33973 33966 -7
+ Misses 56839 56813 -26
Partials 2468 2468 โ View full report in Codecov by Sentry. ๐ New features to boost your workflow:
|
Great job, no security vulnerabilities found in this Pull Request |
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.
These changes make sense.
Non blocking nit: would it make sense to wrap rows in a container to restrict width span?
I had considered that, but being able to see components natural behaviour in isolation is useful too (does the component have a native "size", or does it take over the space of it's container?) and instructional on how it may or may not need to be handled in different contexts. In any case, you can see these cases used in composed situations in other stories, so it didn't feel like a critical need at this point. That said, we do that in some stories (see: Icons), so I could go either way on that, I think. For now I opted to leave it alone and we can revisit in the future. |
๐๏ธ Tracking
PM-21882
๐ Objective
Clean up the Lit component stories a bit
๐ฆฎ Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or โน๏ธ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or ๐ญ (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or โป๏ธ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes