[illustration] update MailSent#2924
Closed
j-mnizhek wants to merge 17 commits into
Closed
Conversation
#2907) …omponents@17.0.2, @semcore/badge@17.0.1, @semcore/breadcrumbs@17.0.1, @semcore/bulk-textarea@17.0.2, @semcore/card@17.0.2, @semcore/button@17.0.1, @semcore/carousel@17.0.1, @semcore/base-trigger@17.0.1, @semcore/checkbox@17.0.2, @semcore/color-picker@17.0.1, @semcore/core@17.0.1, @semcore/d3-chart@17.0.2, @semcore/data-table@17.0.2, @semcore/counter@17.0.1, @semcore/drag-and-drop@17.0.1, @semcore/dot@17.0.2, @semcore/dropdown@17.0.1, @semcore/date-picker@17.0.2, @semcore/divider@17.0.2, @semcore/ellipsis@17.0.1, @semcore/errors@17.0.2, @semcore/feature-highlight@17.0.1, @semcore/dropdown-menu@17.0.1, @semcore/flags@17.0.1, @semcore/feature-popover@17.0.1, @semcore/feedback-form@17.0.1, @semcore/i18n-unplugin@16.0.10, @semcore/fullscreen-modal@17.0.1, @semcore/inline-edit@17.0.1, @semcore/inline-input@17.0.1, @semcore/input@17.0.1, @semcore/input-tags@17.0.1, @semcore/input-number@17.0.1, @semcore/link@17.0.1, @semcore/input-mask@17.0.2, @semcore/mini-chart@17.0.1, @semcore/modal@17.0.1, @semcore/notice@17.0.1, @semcore/pills@17.0.2, @semcore/pagination@17.0.1, @semcore/notice-bubble@17.0.1, @semcore/product-head@17.0.1, @semcore/progress-bar@17.0.2, @semcore/radio@17.0.2, @semcore/select@17.0.1, @semcore/side-panel@17.0.2, @semcore/slider@17.0.1, @semcore/spin@17.0.1, @semcore/skeleton@17.0.2, @semcore/spin-container@17.0.1, @semcore/switch@17.0.1, @semcore/tab-line@17.0.2, @semcore/tab-panel@17.0.2, @semcore/tag@17.0.1, @semcore/textarea@17.0.1, @semcore/time-picker@17.0.1, @semcore/tooltip@17.0.1, @semcore/typography@17.0.2, @semcore/widget-empty@17.0.1, @semcore/add-filter@17.0.1, @semcore/wizard@17.0.1, @semcore/ui@17.0.2 ## Changelog ### @semcore/_$component_name #### Fixed - <!--- 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: semrush-ci-whale <semrush-ci-whale@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.
<!--- 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). - [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: 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 <!--- 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). - [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: Julia Mnizhek <j.mnizhek@semrush.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: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com>
<!--- Provide a general summary of your changes in the Title above --> ## Motivation and Context Small hot fix: removed opacity from active borders and made its Lightness same as our focus styles. ## 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 --> 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. --------- Co-authored-by: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com>
github-actions
Bot
added
illustration
widget-empty
data-table
feedback-form
errors
labels
ilyabrower
force-pushed
the
release/v17
branch
2 times, most recently
from
036c37b to
c160d60
Compare
j-mnizhek
changed the title
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
4 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/illustration
Changed
MailSentillustration. Fixed the tiny issue with the cropped hand.How has this been tested?
Manually with Storybook and documentation.
Screenshots (if appropriate):
Before:
Now (old and new themes):
Tested with color props (old and new themes):
Types of changes
Checklist: