Fix billion suffix logic to handle all positions >= 3 consistently #53
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.



The billion suffix generation used inconsistent code paths: position 3 fell through to a hardcoded return, while positions >= 6 used a formula-based approach. This made the logic harder to reason about and violated the principle of uniform handling.
Changes
positionFromRight >= 6topositionFromRight >= 3, so all billion positions useMath.floor(positionFromRight / 3)to calculate repetitionsArray()withnew Array()per project conventionsThe behavior is unchanged (position 3 still produces ' tỷ'), but the implementation is now consistent across all billion positions.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.