[UIK-5879][d3-chart] area redesign - #3181
ilyabrower wants to merge 164 commits into
Conversation
…elements (#3045) ## Changelog ### @semcore/dropdown-menu #### Fixed - `preventFocusByClick` handler - skip draggable elements. <!--- 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: --> - [X] 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.
…some theme initial fixes (#3057) ## Changelog ### @semcore/button #### Changed - Styles #### Break - Remove legacy `secondary` `info` theme. ### @semcore/theme #### Changed - Values for color variables - Default height for controls: for M — from 28 to 32. for L — from 40 to 44 ### @semcore/link #### Changed - Styles ### @semcore/modal #### Fixed - Hardcoded margins in Close button. ### @semcore/fullscreen-modal #### Fixed - Hardcoded margins in Close button. ## Motivation and Context **Along with button styles and values for its variables, I had to:** - update comments in some components according to the new variables names we were discussing with girls - remove hardcoded margins in Close button component inside the Modal and FullscreModal - remove hardcoded values for w and h in: BaseTrigger, ColorPicker, InputTags, Input, Notice.Label, Pills, TabLine, TimePicker - updated variables' values and styles of the Link ## How has this been tested? Manually. ## Screenshots (if appropriate): Current: <img width="831" height="477" alt="image" src="https://github.com/user-attachments/assets/d59b0010-13e1-404b-88bc-8de25be28d94" /> Updated: <img width="1024" height="524" alt="image" src="https://github.com/user-attachments/assets/ffcdb9ab-5d09-4821-9d69-87601376f362" /> ## Types of changes - [ ] 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). - [x] Nice improve. ## Checklist: - [ ] 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: ilia.brauer <ilia.brauer@semrush.com>
## 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.
## Motivation and Context Updated styles for: - Input - InputNumber - InlineInput - TimePicker Updated: - Button's width and max-width - Link's border-radius to round it's focus outline - A bunch of stories to align them with design requirements ## How has this been tested? Manually. ## Screenshots (if appropriate): ### InlineInput before: <img width="354" height="123" alt="image" src="https://github.com/user-attachments/assets/826125fc-82df-4038-b475-ae304f0d559f" /> <img width="464" height="131" alt="image" src="https://github.com/user-attachments/assets/f8fc06f0-329e-48d4-91fa-f64b63b6709a" /> ### InlineInput after: <img width="318" height="132" alt="image" src="https://github.com/user-attachments/assets/0fad9b3c-03ec-4d9c-974a-aec6bd1a392a" /> <img width="315" height="127" alt="image" src="https://github.com/user-attachments/assets/2114eb5e-ee93-42d1-938d-522acaf7035d" /> ## Types of changes - [ ] 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: - [ ] I have updated the documentation accordingly. - [ ] I have added new tests on added of fixed functionality. --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Slizhevsky Vladislav <uladzislau.slizheuski@semrush.com> Co-authored-by: ilia.brauer <ilia.brauer@semrush.com> Co-authored-by: Valeryia Zimnitskaya <valeryia.zimnitskaya@semrush.com>
|
|
||
| SLinearGradient { | ||
| SStopFrom { | ||
| stop-color: var(--violet-300, oklch(0.74 0.17 303)); |
There was a problem hiding this comment.
@sheila-semrush maybe we should use tokens here?
| } | ||
|
|
||
| SStopTo { | ||
| stop-color: var(--green-100, oklch(0.9 0.11 175)); |
There was a problem hiding this comment.
@sheila-semrush maybe we should use tokens here?
| @@ -1,6 +1,9 @@ | |||
| import { sstyled } from '@semcore/core'; | |||
| import propsForElement from '@semcore/core/lib/utils/propsForElement'; | |||
| import { line } from 'd3-shape'; | |||
There was a problem hiding this comment.
is that necessary import?
| transparent={transparent} | ||
| cx={d3.x()(d)} | ||
| cy={d3.y()(d)} | ||
| r={11.5} |
There was a problem hiding this comment.
@sheila-semrush is that expected that radius is hardcoded here?
| transparent={transparent} | ||
| cx={d3.x()(d)} | ||
| cy={d3.y()(d)} | ||
| r={8.5} |
There was a problem hiding this comment.
@sheila-semrush is that expected that radius is hardcoded here?
|
|
||
| export type ObjectDataKey = string; | ||
| export type ObjectData = Record<ObjectDataKey, unknown>; | ||
| export type ObjectData = Record<ObjectDataKey, number | typeof interpolateValue | Date | string | string[] | number[]> & { |
There was a problem hiding this comment.
Type 'null' is not assignable to type 'string | number | number[] | unique symbol | Date | string[]' - maybe we should support here null too?
…ies/add mock data pipeline/effects to modify data/small utils to compose it
…es triple rendering for forecast/potential dots
| return patterns[patternIndex]; | ||
| }; | ||
|
|
||
| export const DefaultStrokePattern = (props: { id: string }) => { |
There was a problem hiding this comment.
I think DefaultStrokePattern isn't used anywhere anymore (it was added when experimenting with patterns at the very beginning). I guess it can be removed
| <LightStrokePattern id={`${props.id}-stroke`} /> | ||
|
|
||
| <mask id={props.id}> | ||
| <rect width='100%' height='100%' fill={props.color} /> |
There was a problem hiding this comment.
what does this do? (just a question)
Motivation and Context
How has this been tested?
Screenshots (if appropriate):
Types of changes
Checklist: