[UIK-5351][theme] Add more variables to theme - #3039
Open
j-mnizhek wants to merge 71 commits into
Open
Conversation
github-actions
Bot
added
badge
feature-highlight
base-components
base-trigger
select
time-picker
add-filter
date-picker
button
wizard
side-panel
pagination
notice-bubble
feedback-form
modal
fullscreen-modal
carousel
notice
inline-input
feature-popover
errors
dropdown-menu
data-table
color-picker
card
drag-and-drop
bulk-textarea
labels
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context See the list of changes in the task. ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Co-authored-by: ilia.brauer <ilia.brauer@semrush.com> Co-authored-by: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Co-authored-by: Julia Mnizhek <j.mnizhek@semrush.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
## Motivation and Context `Counter`/`Dot` rebranding. ## How has this been tested? Manually ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Julia Mnizhek <j.mnizhek@semrush.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context Pills rebranding. ## How has this been tested? Manually ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [x] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Julia Mnizhek <j.mnizhek@semrush.com> Co-authored-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Co-authored-by: Sheila Sheikh <166654065+sheila-semrush@users.noreply.github.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Co-authored-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Co-authored-by: Julia Mnizhek <j.mnizhek@semrush.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
## Motivation and Context - Updated variables used in FeaturePopover styles - Update its stories ## How has this been tested? Manually. ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [x] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
## Motivation and Context - Updated variables used in the NoticeBubble styles - Made it a little bit bigger ## How has this been tested? Manually. ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [x] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
## Motivation and Context 1. Update variables for Tag 2. Update InputTags and Tag styles 3. Update test story showing Tag in all themes and sizes 4. Update some values in common constants For dev: - [x] Add the `invert` prop for `primary`, `secondary`, and `additional` themes. - [x] Remove the `tag-color` logic for the `secondary` tag. It shouldn't support custom colors. - [x] And of course, take a look at the changes 🙂 ## How has this been tested? Manually, with Storybook and Figma. <img width="961" height="878" alt="image" src="https://github.com/user-attachments/assets/3a0fe9e3-2206-470f-adf0-0a6b53833054" /> ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [x] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: ilia.brauer <ilia.brauer@semrush.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context `Pagination` rebranding. ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
## Motivation and Context - Updated styles for BulkTextarea and Textarea (mostly paddings, margins) - Pulled updates from #3073, because needed them for testing content alignment in different inputs - Added 2 test stories for forms with horizontal and vertical layout ## How has this been tested? Manually. ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [x] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Julia Mnizhek <77798437+j-mnizhek@users.noreply.github.com> Co-authored-by: ilia.brauer <ilia.brauer@semrush.com> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Sheila Sheikh <166654065+sheila-semrush@users.noreply.github.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Sheila Sheikh <166654065+sheila-semrush@users.noreply.github.com> Co-authored-by: Valeria-Zimnitskaya <valeryia.zimnitskaya@semrush.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? <!--- Please describe in detail how you tested your changes. --> <!--- For example: --> <!--- I have added unit tests --> <!--- I have added Voice Over tests --> <!--- Code cannot be tested automatically so I have tested it only manually --> ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue). - [ ] New feature (non-breaking change which adds functionality). - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). - [ ] Nice improve. ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Signed-off-by: ilyabrower <ilya-brower@yandex.ru> Co-authored-by: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com> Co-authored-by: Sheila <166654065+sheila-semrush@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog
@semcore/theme
BREAK
@semcore/accordion
BREAK
@semcore/add-filter
BREAK
@semcore/animation
BREAK
@semcore/badge
BREAK
theme:default | light | invert.inverted.@semcore/base-trigger
BREAK
@semcore/breadcrumbs
BREAK
@semcore/breakpoints
BREAK
@semcore/bulk-textarea
BREAK
@semcore/button
BREAK
@semcore/card
BREAK
@semcore/carousel
BREAK
@semcore/checkbox
BREAK
@semcore/color-picker
BREAK
@semcore/core
BREAK
@semcore/counter
BREAK
@semcore/d3-chart
BREAK
@semcore/data-table
BREAK
@semcore/date-picker
BREAK
@semcore/divider
BREAK
@semcore/dot
BREAK
@semcore/drag-and-drop
BREAK
@semcore/dropdown
BREAK
@semcore/dropdown-menu
BREAK
@semcore/ellipsis
BREAK
@semcore/errors
BREAK
@semcore/feature-highlight
BREAK
@semcore/feature-popover
BREAK
@semcore/feedback-form
BREAK
@semcore/flags
BREAK
@semcore/flex-box
BREAK
@semcore/fullscreen-modal
BREAK
@semcore/grid
BREAK
@semcore/hint
BREAK
@semcore/icon
BREAK
@semcore/illustration
BREAK
@semcore/inline-edit
BREAK
@semcore/inline-input
BREAK
@semcore/input
BREAK
@semcore/input-mask
BREAK
@semcore/input-number
BREAK
@semcore/input-tags
BREAK
@semcore/link
BREAK
@semcore/mini-chart
BREAK
@semcore/modal
BREAK
@semcore/neighbor-location
BREAK
@semcore/notice
BREAK
@semcore/notice-bubble
BREAK
@semcore/outside-click
BREAK
@semcore/pagination
BREAK
@semcore/pills
BREAK
@semcore/popper
BREAK
@semcore/portal
BREAK
@semcore/product-head
BREAK
@semcore/progress-bar
BREAK
@semcore/radio
BREAK
@semcore/scroll-area
BREAK
@semcore/select
BREAK
@semcore/side-panel
BREAK
@semcore/skeleton
BREAK
@semcore/slider
BREAK
@semcore/spin
BREAK
@semcore/spin-container
BREAK
@semcore/switch
BREAK
@semcore/tab-line
BREAK
@semcore/tab-panel
BREAK
@semcore/tag
BREAK
@semcore/textarea
BREAK
@semcore/time-picker
BREAK
@semcore/tooltip
BREAK
@semcore/typography
BREAK
@semcore/widget-empty
BREAK
@semcore/wizard
BREAK
Motivation and Context
How has this been tested?
Manually.
Types of changes
Checklist: