Skip to content

[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

Merged
merged 4 commits into from
May 22, 2025
Merged

[PM-21882] Lit Components Cleanup #14872

merged 4 commits into from
May 22, 2025

Conversation

jprusik
Copy link
Contributor

@jprusik jprusik commented May 21, 2025

๐ŸŽŸ๏ธ 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

@jprusik jprusik requested a review from a team as a code owner May 21, 2025 21:11
@jprusik jprusik self-assigned this May 21, 2025
Copy link
Contributor Author

@jprusik jprusik May 21, 2025

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)

Copy link

codecov bot commented May 21, 2025

Codecov Report

Attention: Patch coverage is 0% with 15 lines in your changes missing coverage. Please review.

Project coverage is 36.42%. Comparing base (f0b2551) to head (d352a6b).
Report is 7 commits behind head on main.

โœ… All tests successful. No failed tests found.

Files with missing lines Patch % Lines
...utofill/content/components/rows/cipher-item-row.ts 0.00% 7 Missing โš ๏ธ
...ts/lit-stories/rows/cipher-item-row.lit-stories.ts 0.00% 4 Missing โš ๏ธ
...ponents/lit-stories/rows/button-row.lit-stories.ts 0.00% 2 Missing โš ๏ธ
...c/autofill/content/components/notification/body.ts 0.00% 2 Missing โš ๏ธ
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.
๐Ÿ“ข Have feedback on the report? Share it here.

๐Ÿš€ New features to boost your workflow:
  • ๐Ÿ“ฆ JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

Logo
Checkmarx One โ€“ Scan Summary & Details โ€“ 003aa3f5-6536-47a3-83f4-4b5612be9b10

Great job, no security vulnerabilities found in this Pull Request

Copy link
Collaborator

@dan-livefront dan-livefront left a 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?

@jprusik
Copy link
Contributor Author

jprusik commented May 22, 2025

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.

@jprusik jprusik merged commit 753e7af into main May 22, 2025
48 checks passed
@jprusik jprusik deleted the pm-21882 branch May 22, 2025 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants