"i18n": [false,"check-text"] fails on text containing only non-word characters
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
Is there a way to use the `"i18n": [false,"check-text"]` rule would pass for any text node containing only numbers or other non-word symbols even if the wrapper element is missing the `i18n` attribute?
If not, could this be added as a config option?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation and tests for the i18n check-text rule, then reproduce the behavior with text nodes containing only numbers or other non-word symbols. Determine whether the rule can pass those nodes without a wrapper i18n attribute or needs a configuration option; done means the chosen behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- internationalization, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100