Skip to content

[UIK-5879][d3-chart] area redesign - #3181

Open
ilyabrower wants to merge 164 commits into
release/v18from
UIK-5879/d3-chart-area-redesign
Open

ilyabrower wants to merge 164 commits into
release/v18from
UIK-5879/d3-chart-area-redesign

Conversation

@ilyabrower

Copy link
Copy Markdown
Contributor

Motivation and Context

How has this been tested?

Screenshots (if appropriate):

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).
  • Nice improve.

Checklist:

  • I have updated the documentation accordingly.
  • I have added new tests on added of fixed functionality.

j-mnizhek and others added 30 commits June 30, 2026 17:45
…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>
Comment thread semcore/d3-chart/src/component/Chart/AreaChart.type.ts

SLinearGradient {
SStopFrom {
stop-color: var(--violet-300, oklch(0.74 0.17 303));

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.

@sheila-semrush maybe we should use tokens here?

}

SStopTo {
stop-color: var(--green-100, oklch(0.9 0.11 175));

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.

@sheila-semrush maybe we should use tokens here?

Comment thread semcore/d3-chart/src/Pattern.tsx Outdated
@@ -1,6 +1,9 @@
import { sstyled } from '@semcore/core';
import propsForElement from '@semcore/core/lib/utils/propsForElement';
import { line } from 'd3-shape';

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.

is that necessary import?

transparent={transparent}
cx={d3.x()(d)}
cy={d3.y()(d)}
r={11.5}

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.

@sheila-semrush is that expected that radius is hardcoded here?

transparent={transparent}
cx={d3.x()(d)}
cy={d3.y()(d)}
r={8.5}

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.

@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[]> & {

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.

Type 'null' is not assignable to type 'string | number | number[] | unique symbol | Date | string[]' - maybe we should support here null too?

Base automatically changed from UIK-5830/d3-chart-tooltip-rebranding to release/v18 September 22, 2026 12:06
return patterns[patternIndex];
};

export const DefaultStrokePattern = (props: { id: string }) => {

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.

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} />

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.

what does this do? (just a question)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants