Skip to content

[UIK-5881][d3-chart] donut rebranding/change only default donut thickness - #3201

Merged
Valeria-Zimnitskaya merged 1 commit into
release/v18from
UIK-5881/d3-chart-donut-rebranding
Oct 1, 2026
Merged

Valeria-Zimnitskaya merged 1 commit into
release/v18from
UIK-5881/d3-chart-donut-rebranding

Conversation

@slizhevskyv-semrush

Copy link
Copy Markdown
Contributor

Changelog

@semcore/d3-chart

Changed

  • Default Donut thickness to 12.

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.

@Valeria-Zimnitskaya
Valeria-Zimnitskaya merged commit 1d79275 into release/v18 Oct 1, 2026
14 checks passed
@Valeria-Zimnitskaya
Valeria-Zimnitskaya deleted the UIK-5881/d3-chart-donut-rebranding branch October 1, 2026 14:56
slizhevskyv-semrush added a commit that referenced this pull request Oct 1, 2026
@slizhevskyv-semrush
slizhevskyv-semrush restored the UIK-5881/d3-chart-donut-rebranding branch October 1, 2026 15:18
ilyabrower pushed a commit that referenced this pull request Oct 7, 2026
…ness (#3201)

## Changelog

### @semcore/d3-chart

#### Changed

- Default `Donut` thickness to `12`.

<!--- 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.
ilyabrower pushed a commit that referenced this pull request Oct 7, 2026
ilyabrower pushed a commit that referenced this pull request Oct 8, 2026
…ness (#3201)

<!--- 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.
ilyabrower pushed a commit that referenced this pull request Oct 8, 2026
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.

3 participants