Rule Proposal: prefer-numeric-literals
See original GitHub issueFrom requireNumericLiterals.
This rule will disallow parseInt
with a constant value as the favor of numeric literals.
{
"prefer-numeric-literals": "error"
}
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
prefer-numeric-literals - ESLint - Pluggable JavaScript Linter
This rule disallows calls to parseInt() or Number.parseInt() if called with two arguments: a string; and a radix option of 2 (binary), 8...
Read more >Proposal: Go 2 Number Literal Changes
We propose four related changes to number literals in Go: Add binary integer literals, as in 0b101. Add alternate octal integer literals, as...
Read more >[Returned for Revision] SE-0354: Regex Literals - Swift Forums
Hi everyone, The review of SE-0354: Regex Literals ran from April 28 to May 10. The core team has decided to return the...
Read more >PEP 515 – Underscores in Numeric Literals
The current proposal is to allow one underscore between digits, and after base specifiers in numeric literals. The underscores have no semantic meaning, ......
Read more >Google JavaScript Style Guide
5 Language features: 5.1 Local variable declarations: 5.2 Array literals ... Like other programming style guides, the issues covered span not only aesthetic ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can probably take this one (made the JSCS rule originally)
@azhang496 said she would take this (I’m guiding/helping)