Skip to content

refactor button styles implementation to more maintainable approach w…#4698

Draft
mark-tate wants to merge 2 commits intomainfrom
refactor-button-styles
Draft

refactor button styles implementation to more maintainable approach w…#4698
mark-tate wants to merge 2 commits intomainfrom
refactor-button-styles

Conversation

@mark-tate
Copy link
Contributor

…ith simpler naming

@changeset-bot
Copy link

changeset-bot bot commented Feb 11, 2025

🦋 Changeset detected

Latest commit: a9ed8a9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@salt-ds/core Patch
@salt-ds/countries Patch
@salt-ds/data-grid Patch
@salt-ds/lab Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Feb 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
saltdesignsystem ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 28, 2025 2:00pm

@origami-z
Copy link
Contributor

before i forget, one of the reasons this was needed, was to enable cross component override (e.g. Icon). More testing is needed to confirm whether 1 type of variable is enough, and/or alternative approach


Refactor internal implementation of button styles

- this is a non-breaking refactor of how we organise the styles within the CSS file.
Copy link
Contributor

Choose a reason for hiding this comment

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

checking, is this definitely considered non breaking/..only a patch? I personally have used a lot of --saltComponent tokens myself which would have to be changed by this

@origami-z origami-z marked this pull request as draft April 24, 2025 07:41
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.

4 participants