feat(numeric-keyboard): expose keypad input rules for hardware keyboards

[romchornyi]

Issue being fixed or feature implemented

NumericKeyboardView renders buttons and installs no text responder, so digits typed on a connected physical keyboard never reach it. A host that wants hardware-keyboard support has to add its own responder — and then it needs the pad's input rules, which were internal to the package.

The first host to do this (dashwallet-ios #1040) reimplemented them app-side and got the locale handling wrong: it mapped , to the decimal separator in every locale, so typing 1,000 in en_US produced 1.000 — a silent 1000x error on the send and pay screens. The on-screen pad, which routes through applyKeyPress, drops the locale's grouping separator and gets 1000.

What was done?

• Made NumericKeyboardLocaleSupport public, along with applyKeyPress, decimalSeparator(for:) and a new deleteKey.
• Added key(forTyped:locale:), which translates a character typed on a physical keyboard into the key the on-screen pad would have sent, or nil when the pad has no such key.

The locale-sensitive rules — which separator is decimal, which is grouping and therefore dropped, at most one decimal separator, delete — stay in applyKeyPress alone. key(forTyped:) deliberately passes the grouping separator through untouched instead of filtering it, so that rule has exactly one implementation and both input paths agree by construction.

No behavior change for existing callers: the on-screen pad's code path is untouched, and the change to the type's surface is internal → public.

How Has This Been Tested?

• swift build -c release — clean.
• swift test --filter NumericKeyboardLocaleSupportTests — 8 tests, 0 failures.
• New cases cover the character mapping, the locale-dependent decimal key (en_US, de_DE, and de_CH where the typed character is neither separator), and that typing a grouped amount keeps its magnitude in both en_US (1,000.5 → 1000.5) and de_DE (1.000,5 → 1000,5).

Breaking Changes

None.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d0ebcd7-5196-41c4-90a6-7249115da2e7

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[llbartekll]

Looks good