Skip to content

Make large numbers easier to read #15563

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

Closed
mlongtin0 opened this issue Jun 16, 2023 · 4 comments
Closed

Make large numbers easier to read #15563

mlongtin0 opened this issue Jun 16, 2023 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@mlongtin0
Copy link

mlongtin0 commented Jun 16, 2023

Description of the new feature/enhancement

Large numbers like "16000000" are hard to read in a monitor. Is it 1.6, 16 or 160 millions? I end up trying to select groups of three to make sense of it.

I would like to propose to italicize or bold alternating groups, like this: 16000000 or 16000000
This would be enough to make it easier to read. The grouping should be customizable.

Proposed technical implementation details (optional)

@mlongtin0 mlongtin0 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 16, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 16, 2023
@lhecker
Copy link
Member

lhecker commented Jun 16, 2023

I feel like such an addition might be a little too niche. Is there a reason your application couldn't just format numbers in a more legible way in the first place?

@mlongtin0
Copy link
Author

I deal with large numbers all the time, the basic tools don't format, so I end up having to pipe through a number formatter. Even the default Excel is painful that way.

A less niche version would be some sort of regex transform that's applied to the display. It could be used to always put ERROR in bold and red, for example.

@lhecker lhecker added the Needs-Discussion Something that requires a team discussion before we can proceed label Jun 16, 2023
@zadjii-msft
Copy link
Member

A less niche version would be some sort of regex transform that's applied to the display. It could be used to always put ERROR in bold and red, for example

Thats in #5916. dunno if the spec I have in progress would adequately cover this tho

@mlongtin0
Copy link
Author

Correct. Duplicate of #6297.

@mlongtin0 mlongtin0 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2023
@zadjii-msft zadjii-msft removed the Needs-Discussion Something that requires a team discussion before we can proceed label Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

3 participants