-
Notifications
You must be signed in to change notification settings - Fork 4k
Limit displayed Exchange Rate values to 4 decimals in expense tables #98620
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 The exponential case is only tested through the
numberfield, not thestringfield where the bug was actually reported.tests/unit/TransactionUtilsTest.ts(theformats an exponential rate to 0.0000case)The test drives it through
groupExchangeRate: 7.27431439586819e-7, which is typednumber. The screenshot in the issue shows the bug arriving throughcurrencyConversionRate, which is typedstring, so the real input is the string'7.27431439586819e-07', complete with the zero-padded exponent.Number()parses both, so this passes today, but the two branches read different fields of different types and only one of them is covered for the input class that motivated the issue. One extra case:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in eef0158. New case
formats an exponential rate string to 0.0000drives the exponential rate throughcurrencyConversionRateas the zero-padded string'7.27431439586819e-07'— thestringfield and exact input class from the reported screenshot — alongside the existingnumber-field case. Both pass.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in
eef0158. Added a case that drives the exponential input throughcurrencyConversionRate(typedstring) using the zero-padded exponent string'7.27431439586819e-07', which is the form the reported bug actually arrived in, and asserts'0.0000 IRR/USD'. All 22getExchangeRatetests pass.