Skip to content

feat(theme): update classic theme styles and fix hover/active#2511

Open
danielleroux wants to merge 1 commit intomainfrom
chore/4197-update-theme
Open

feat(theme): update classic theme styles and fix hover/active#2511
danielleroux wants to merge 1 commit intomainfrom
chore/4197-update-theme

Conversation

@danielleroux
Copy link
Copy Markdown
Collaborator

💡 What is the current behavior?

Jira: [IX-4197]

🆕 What is the new behavior?

Update to latest design tokens

🏁 Checklist

A pull request can only be merged if all of these conditions are met (where applicable):

  • 🦮 Accessibility (a11y) features were implemented
  • 🗺️ Internationalization (i18n) - no hard coded strings
  • 📲 Responsiveness - components handle viewport changes and content overflow gracefully
  • 📕 Add or update a Storybook story
  • 📄 Documentation was reviewed/updated siemens/ix-docs
  • 🧪 Unit tests were added/updated and pass (pnpm test)
  • 📸 Visual regression tests were added/updated and pass (Guide)
  • 🧐 Static code analysis passes (pnpm lint)
  • 🏗️ Successful compilation (pnpm build, changes pushed)

👨‍💻 Help & support

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the classic theme by fixing hover and active states for buttons, chips, links, and invalid switches, while also aligning theme variable application with data-attribute selectors. The review feedback identifies that the removal of body class selectors is a breaking change, necessitating a major version bump in the changeset and a corresponding update to the PR title. Furthermore, the reviewer pointed out that manual modifications to auto-generated SCSS files should be moved to the source definitions to prevent them from being overwritten.

Comment on lines +1 to +5
---
'@siemens/ix': patch
---

Fix classic theme hover and active states for buttons, chips, links, and invalid switches, and align classic light and dark variable application with the supported data-attribute theme selectors.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The removal of the body class selectors in the theme index files is a breaking change. According to the Repository Style Guide (Rule 39), major changes must be clearly described in the changeset with migration steps. Additionally, the PR title should be updated to include a ! (e.g., feat(theme)!) to signal the breaking change (Rule 16). Finally, please ensure visual regression tests are updated as they are currently unchecked in the PR description (Rule 59).

Suggested change
---
'@siemens/ix': patch
---
Fix classic theme hover and active states for buttons, chips, links, and invalid switches, and align classic light and dark variable application with the supported data-attribute theme selectors.
---
'@siemens/ix': major
---
Fix classic theme hover and active states for buttons, chips, links, and invalid switches.
### Breaking Change
The body[class*="theme-classic-dark"] and body[class*="theme-classic-light"] selectors have been removed. Use the data-attribute selectors [data-ix-theme="classic"][data-ix-color-schema="dark|light"] instead.
References
  1. If the change is major, ensure that the changeset summary clearly describes the breaking nature of the change and the migration steps consumers need. (link)

--theme-color-neutral-40: rgba(182, 184, 185, 0.4);
--theme-color-primary: #00bde3;
--theme-color-primary--active: #00eaff;
--theme-color-primary--active: #00d3e5;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

This file is marked as auto-generated. Manual edits will be overwritten by the build process. Please ensure these token updates are made in the source definitions and propagated via the generation script. This applies to all SCSS files modified in this PR. Note that new properties should also include @SInCE tags in the source to comply with Rule 67.

References
  1. Ensure that each new component, property, method, or event has a JSDocs which contains a @SInCE tag with the version number of the release in which it was added. (link)
  2. Do not suggest manual edits for auto-generated files, as changes will be overwritten by the build process.

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.

1 participant