tweak(tupaiaWeb): format numbers with thousands separators#6635
tweak(tupaiaWeb): format numbers with thousands separators#6635jaskfla wants to merge 6 commits into
Conversation
Summary of ChangesHello @jaskfla, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly upgrades the application's data formatting utility, Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request enhances number formatting by adding thousands separators, which improves readability. The changes are well-tested with a comprehensive suite of new unit tests covering various data types and edge cases, including negative values. The codebase is also improved by using modern JavaScript features like nullish coalescing and const assertions for better type safety.
My main feedback is regarding a workaround for a numeral.js bug, where I've suggested an improvement for better code clarity and maintainability.
ea0b7ab to
7363be6
Compare
26efcf8 to
9718802
Compare
3620213 to
2fe6afb
Compare
edf2493 to
ebbcd74
Compare
ignores locale, though 😔
ebbcd74 to
bba1bde
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| NUMBER: 'number', | ||
| ONE_DECIMAL_PLACE: 'oneDecimalPlace', | ||
| }; | ||
| }); |
There was a problem hiding this comment.
Missing thousands separator in numberAndPercentage formatter
Medium Severity
The numberAndPercentage formatter displays the value without thousands separators. When displaying values >= 1,000 (e.g., "1000 (50.0%)"), they appear without commas, inconsistent with the PR's goal to format numbers with thousands separators. The value part needs formatting with numeral(value).format('0,0') to display as "1,000 (50.0%)".
| NUMBER: 'number', | ||
| ONE_DECIMAL_PLACE: 'oneDecimalPlace', | ||
| }; | ||
| }); |
There was a problem hiding this comment.
Missing thousands separators in fractionAndPercentage formatter
Medium Severity
The fractionAndPercentage formatter displays numerator and denominator without thousands separators. Values >= 1,000 appear as "1000/2000 = 50.0%" instead of "1,000/2,000 = 50.0%", inconsistent with the PR's goal. Both numerator and denominator need formatting with numeral() to properly display large numbers.
| NUMBER: 'number', | ||
| ONE_DECIMAL_PLACE: 'oneDecimalPlace', | ||
| }; | ||
| }); |
There was a problem hiding this comment.
Missing thousands separators in fraction formatter
Medium Severity
The fraction formatter uses String(value) and String(total) which don't add thousands separators. Large values display as "1000/5000" instead of "1,000/5,000", inconsistent with the PR's intent. Both values need formatting with numeral() to match the thousands separator treatment in other formatters.


No description provided.