Rule: prefer N/format when formatting dates and other supported values
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start by reading the existing rule implementations and docs/rule-priority.md to see how rules are structured and assigned to presets. Then define which native formatting patterns N/format should replace and how to avoid flagging intentional formats such as ISO strings for external APIs. Done means the rule detects supported cases with those false positives addressed, and its severity and preset placement are documented.
Written by the indexing model from the issue text.
Description
TODO: add a rule that prefers N/format (format.format / format.parse) when formatting or parsing dates and other values N/format supports, instead of native approaches such as Date.prototype.toLocaleDateString, toISOString string slicing, Intl.*, or manual string building.
Open questions for triage:
- Which native patterns reliably indicate a value that
N/formatshould handle (dates, datetimes, currency, numbers, percents, etc. performat.Type). - How to avoid false positives where native formatting is intended (e.g. ISO strings for external APIs).
- Default severity and preset placement per
docs/rule-priority.md.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 64
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from nemchik/biome-plugin-suitescript
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
nemchik/biome-plugin-suitescript#137 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nemchik/biome-plugin-suitescript#87 ·
Maintainers usually reply within 1 day
-
enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nemchik/biome-plugin-suitescript#48 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 3/5 Half a day Newbie friendliness 45/100
nemchik/biome-plugin-suitescript#138 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nemchik/biome-plugin-suitescript#136 ·
Maintainers usually reply within 1 day
All issues in nemchik/biome-plugin-suitescript
Similar issues
-
parse: child keys like `007`, `1e3`, `0x1f`, `-1` make the parent an empty array and hide the valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
bketelsen/pi-pocket-team#232 ·
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
area: interop area: sip-core v3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fonoster/routr#705 · 1 comment ·
Maintainers usually reply within 1 day