feat(pinCodeInput): add optional keyboardType (numeric/alphanumeric)

[theamiri]

Related issues

Closes #733

Description

Adds an optional keyboardType parameter on OudsDigitInputDecoration, exposed publicly via a new enum OudsPinCodeInputKeyboardType with two values: numeric (default) and alphanumeric.

• When set to numeric, the per-digit TextField requests TextInputType.number and rejects non-digit input via FilteringTextInputFormatter.digitsOnly. The paste handler in OudsPinCodeInput also sanitizes the incoming string to digits only before populating the cells.
• When set to alphanumeric, the field requests TextInputType.text and accepts any character (typed or pasted).

The default is numeric, so existing call sites are unaffected. The demo app exposes the option as a chip group in the PIN code input customization sheet, the code generator emits the parameter only when non-default, and the new label is localized in EN / FR / AR.

Motivation & Context

The PIN code input was hard-wired to TextInputType.number with no input formatter, so the soft keyboard was always digits-only but the component silently accepted non-digit input via paste or a hardware keyboard. Some flows reusing this component need short alphanumeric verification or recovery codes; today they fall back to a plain OudsTextInput and lose the per-digit cell layout, focus shifting, masking, and design system styling. This change closes both gaps with a single optional parameter.

Types of change

• New feature (non-breaking change which adds functionality)

Previews

Checklist

Contribution

• I have read the contributing guidelines

Accessibility

• My change follows accessibility good practices

Design

• My change respects the design guidelines of Orange Unified Design System

Development

• My change follows the developer guide
• (NA) I have added unit tests to cover my changes (optional)

Documentation

• My change introduces changes to the documentation and/or I have updated the documentation accordingly

Checklist (for Core Team only)

• Manually test (dark mode, RTL, landscape display, tablet)
• Documentation has been updated if relevant
• Design review
• A11y review
• Internal files have been updated if relevant (THIRD_PARTY, NOTICE)
• CHANGELOG.md files have been updated respecting keep a changelog rules and referencing the issue

[AhmedAmineZr]

update changelog with number of ticket and update the branch

[theamiri]

Hi,

The two PRs are already open in Orange-OpenSource/ouds-flutter:

• feat(pinCodeInput): add optional keyboardType (numeric/alphanumeric) #734 — feat(pinCodeInput): add optional keyboardType (numeric/alphanumeric) (closes [Component] PinCodeInput: optional keyboardType (numeric / alphanumeric) #733)
  feat(pinCodeInput): add optional keyboardType (numeric/alphanumeric) #734
• fix(pinCodeInput): delete previous digit instantly on backspace #736 — fix(pinCodeInput): delete previous digit instantly on backspace (closes [Bug] PinCodeInput: deletion requires two backspace presses on a typed digit #735)
  fix(pinCodeInput): delete previous digit instantly on backspace #736

Both target develop, both have the CHANGELOG entry, both are now mergeable after the rebase you asked for.

What you're probably seeing is that the source branches live on my fork (theamiri/ouds-flutter) — that's because my account only has read access on the org repo (verified: permissions: { pull: true, push: false }), so GitHub's standard external-contributor flow is "branch on fork → PR upstream". The PRs themselves are in your repo and behave exactly like internal ones for review and merge.

If you'd prefer the branches to live directly inside Orange-OpenSource/ouds-flutter, you'd need to grant me Write/Triage on the repo and I'll push them over. Otherwise there's nothing else to create — let me know if I'm missing something.

Thanks,
Amir