Skip to content

WEBDEV-8100 Encapsulate style settings#22

Merged
rebecca-shoptaw merged 11 commits into
mainfrom
webdev-8100-encapsulate-style-settings
Jan 15, 2026
Merged

WEBDEV-8100 Encapsulate style settings#22
rebecca-shoptaw merged 11 commits into
mainfrom
webdev-8100-encapsulate-style-settings

Conversation

@rebecca-shoptaw

Copy link
Copy Markdown
Collaborator

Encapsulates the style settings options into the story template, so consumers don't have to build out the inputs individually

@codecov-commenter

codecov-commenter commented Jan 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.00%. Comparing base (c62bd53) to head (fa5ee36).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage   60.00%   60.00%           
=======================================
  Files           5        5           
  Lines          45       45           
  Branches        5        5           
=======================================
  Hits           27       27           
  Misses         15       15           
  Partials        3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jbuckner jbuckner left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahhh I love this! 🫶 Thanks for doing this! A few suggestions, but overall looks great!

Comment thread demo/story-template.ts Outdated
Comment thread demo/story-template.ts Outdated
Comment thread demo/story-template.ts Outdated
@jbuckner

Copy link
Copy Markdown
Collaborator

Just thinking out loud here, not for this MR, but it'd be great to have something similar to this for component properties as well... ie

<ia-button .mode=${'danger'}> // ie automatically write out that `.mode=` prop

@rebecca-shoptaw

Copy link
Copy Markdown
Collaborator Author

Just thinking out loud here, not for this MR, but it'd be great to have something similar to this for component properties as well... ie

<ia-button .mode=${'danger'}> // ie automatically write out that `.mode=` prop

@jbuckner 100%! That was one of my bigger motivations in doing this encapsulation, I figured it would help start to set the standards for doing something similar with properties, which will be more complicated, but I think definitely doable.

I'll try to do some similar local consolidation where possible as I add more properties to the status indicator to experiment with what kinds of things would work before doing a full encapsulation

@jbuckner

Copy link
Copy Markdown
Collaborator

Oh something I just noticed.. can we hide the Settings section if we don't have anything in there? (this is the ia-button story)
Screenshot 2026-01-15 at 11 18 19

@rebecca-shoptaw

Copy link
Copy Markdown
Collaborator Author

Oh something I just noticed.. can we hide the Settings section if we don't have anything in there? (this is the ia-button story) Screenshot 2026-01-15 at 11 18 19

We definitely can! I was being lazy and was going to leave that to the property extraction portion of the job (similarly to how the styles section isn't displayed if there are no styles, but I can add a workaround for now if you think we need it.

@jbuckner

Copy link
Copy Markdown
Collaborator

Oh something I just noticed.. can we hide the Settings section if we don't have anything in there? (this is the ia-button story) Screenshot 2026-01-15 at 11 18 19

We definitely can! I was being lazy and was going to leave that to the property extraction portion of the job (similarly to how the styles section isn't displayed if there are no styles, but I can add a workaround for now if you think we need it.

Ah that's fine! Not needed now!

@rebecca-shoptaw

Copy link
Copy Markdown
Collaborator Author

Oh something I just noticed.. can we hide the Settings section if we don't have anything in there? (this is the ia-button story) Screenshot 2026-01-15 at 11 18 19

We definitely can! I was being lazy and was going to leave that to the property extraction portion of the job (similarly to how the styles section isn't displayed if there are no styles, but I can add a workaround for now if you think we need it.

Ah that's fine! Not needed now!

Oops I already did it! But it was good further practice re: dealing with slots and should be easy to switch out.

@rebecca-shoptaw rebecca-shoptaw merged commit 99fce05 into main Jan 15, 2026
1 check passed
@rebecca-shoptaw rebecca-shoptaw deleted the webdev-8100-encapsulate-style-settings branch January 15, 2026 19:53
jbuckner added a commit that referenced this pull request Jan 26, 2026
* main:
  v0.1.0 (#26)
  WEBDEV-8109 Expand status indicator capabilities (#23)
  WEBDEV-8100 Encapsulate style settings (#22)
  Load snowflakes async (#12)
  WEBDEV-8019 Add basic loading indicator (#17)
  Fix issue with css property values not updating (#19)
  WEBDEV-8098: Component Demo Light Mode (#18)
  WEBDEV-8037 Create CSS theme structure (#16)
jbuckner added a commit that referenced this pull request Jan 29, 2026
* main:
  Update directory paths for GitHub Pages (#27)
  WEBDEV-8141: Github Pages (#25)
  v0.1.0 (#26)
  WEBDEV-8109 Expand status indicator capabilities (#23)
  WEBDEV-8100 Encapsulate style settings (#22)
  Load snowflakes async (#12)
  WEBDEV-8019 Add basic loading indicator (#17)
  Fix issue with css property values not updating (#19)
  WEBDEV-8098: Component Demo Light Mode (#18)
  WEBDEV-8037 Create CSS theme structure (#16)
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.

3 participants