Fixing Currency Conversion Glitch: Ensuring Accuracy and Precision #102
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Encountering a conversion rate below 0.9 from the source currency to the target currency, along with the absence of cents in the currency, can be quite tricky during conversion. This unexpected shift of the decimal point to the left by two places isn't something we want happening! So, I'm stepping in with a pull request to fix this issue. It's all about making sure currency conversion is smooth and accurate for everyone involved!
For instance, 2,525,600 yen converted at a rate of 0.031 should indeed give you around 77,778.38 in MYR, but it seems to be returning 777.78 instead