Skip to content

fix(ClusterMetricsCores): format value and capacity same way #1532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 28, 2024
Merged

Conversation

Raubzeug
Copy link
Contributor

@Raubzeug Raubzeug commented Oct 24, 2024

Stand

CI Results

Test Status: ✅ PASSED

📊 Full Report

Total Passed Failed Flaky Skipped
134 134 0 0 0

Bundle Size: 🔺

Current: 79.11 MB | Main: 79.10 MB
Diff: +0.01 MB (0.01%)

⚠️ Bundle size increased. Please review.

ℹ️ CI Information
  • Test recordings for failed tests are available in the full report.
  • Bundle size is measured for the entire 'dist' directory.
  • 📊 indicates links to detailed reports.
  • 🔺 indicates increase, 🔽 decrease, and ✅ no change in bundle size.

* @returns size to format value to get required number of digits
*
* By default value converted to the next size when it's above 1000,
* so we have 900mb and 1gb. To extend it additional significantDigits could be set
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose mb and gb are not accurate examples as gb is 1024mb

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh this terrible copy-paste -_-

@@ -1,8 +0,0 @@
{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Time ago decided not to support /ru localization and if change en keysets, remove ru version

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I remember we decided to support ru localization

@@ -0,0 +1,107 @@
import {formatNumber, roundToPrecision} from '../dataFormatters/dataFormatters';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose formatNumber shouldn't be in bytesParsers as it has small relevance to bytes operations logics

export const getNumberWithSignificantDigits = (value: number, significantDigits: number) => {
const multiplier = 10 ** significantDigits;

const thousandLevel = sizes.million.value * multiplier;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thousand.value

@Raubzeug Raubzeug requested a review from astandrik October 28, 2024 11:33
@Raubzeug Raubzeug requested a review from astandrik October 28, 2024 13:07
@Raubzeug Raubzeug enabled auto-merge October 28, 2024 13:10
@Raubzeug Raubzeug added this pull request to the merge queue Oct 28, 2024
Merged via the queue into main with commit 4eb5c04 Oct 28, 2024
4 of 6 checks passed
@Raubzeug Raubzeug deleted the fix-cores branch October 28, 2024 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants