docs: record the considered-but-not-committed backlog - #19
Merged
Conversation
The roadmap went empty after v0.6, but the ideas that were weighed and set aside had nowhere to live, so the same discussion would just get re-run. docs/backlog.md keeps them with the reasoning: in-field prefix/suffix (the one real gap against AutoNumeric and react-number-format — the read side already works, the cost is caret math, which is this library's most delicate part), and the undecided Korean reading of negative amounts (currently '-987만 6,543', neither documented nor pinned by a test). Also records the signal the decision rests on (0 issues ever, ~12 weekly downloads as of 2026-08-09) and the rule being applied — demand-gated, an entry here is not a promise — so a future reader knows these were choices, not oversights.
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
1 participant
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 roadmap went empty after v0.6, but the ideas weighed and set aside had nowhere to live — so the same discussion would just get re-run later.
docs/backlog.mdkeeps them with the reasoning, linked from both READMEs:₩ 1,234,567,12 %) — the one real gap against AutoNumeric / react-number-format. Notes that the read side already works (parse('₩ 1,234,567원')→'1234567') and that the cost is display + caret math, since affixes are non-significant characters the caret model must never count or let you delete into. Harder than the lakh work, which needed no caret changes.toKorean('-9876543')→"-987만 6,543". A product decision (banking UIs differ), currently neither documented nor pinned by a test.It also records the signal the call rests on (0 issues ever, ~12 weekly downloads as of 2026-08-09) and the rule — demand-gated, an entry is not a promise — so a future reader can tell these were choices rather than oversights.
Docs only; no version bump (nothing to republish for).