Fix float display to always show .0 for integer floats (closes #60) #63
Conversation
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
martin-henz
reviewed
Jul 18, 2025
| @@ -1599,7 +1599,7 @@ export function toPythonFloat(num: number): string { | |||
| return num.toExponential().replace(/e([+-])(\d)$/, 'e$10$2'); | |||
| } | |||
| if (Number.isInteger(num)) { | |||
| return num.toFixed(1).toString(); | |||
| return num.toFixed(1); | |||
There was a problem hiding this comment.
I can't see how this can fix the bug. I agree that the toString is not needed and should be removed. But toFixed already produces a string, and toString will not change the string. So this change should be functionally neutral.
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.
Fix #60 by removing calling of toString for floats