use different output styles for SOL depending on its magnitude#28
Merged
SvenDowideit merged 2 commits intomainfrom Mar 2, 2022
Merged
use different output styles for SOL depending on its magnitude#28SvenDowideit merged 2 commits intomainfrom
SvenDowideit merged 2 commits intomainfrom
Conversation
SvenDowideit
force-pushed
the
feat/variable-solAmount-rendering
branch
from
237dba6 to
cb36aae
Compare
SvenDowideit
force-pushed
the
feat/variable-solAmount-rendering
branch
from
cb36aae to
b69d5ac
Compare
…ect of deploying a program
Contributor
|
LGTM |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
now viewing an account can show
0.000918720,499.961315,499999999,I imagine more tweaking will be needed, but \0/ i made a change :D
(mmm, it might just be that toPrecision() made the most sense?)