how to deal with optional characters
Open
design needed
enhancement
help wanted
- Dominant language
- JavaScript
- Stars
- 303
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
For example, the bold number is "optional", not always required:
value:
55 48 **2**332-4456
suggestion of mask:
11 11 **(1)?**1111-1111
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the mask parsing and character-matching entry points in inputmask-core, then compare their current behavior with the issue's optional-character example. Define how an optional digit should behave for both matching and formatting, and add coverage for the shown mask and value before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100