Rule Proposal: no-spaced-func with never
See original GitHub issueFrom requireSpacesInCallExpression and disallowSpacesInCallExpression.
In JSCS, we can specify that spaces are required before the open parenthesis of call expressions. In ESLint, no-spaced-func has a responsibility for spacing of call expressions.
This proposal is to add "always"
/"never"
option to no-spaced-func.
Maybe we should rename this rule to call-spacing
or something like.
{
"call-spacing": ["error", "always" or "never"]
}
"always"
- Requires spacing before the open parenthesis of call expressions."never"
(default) - Disallows spacing before the open parenthesis of call expressions. (the current behavior)
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
SEC Proposed Rules
SEC Proposed Rules · Regulation NMS: Minimum Pricing Increments, Access Fees, and Transparency of Better Priced Orders · File No: S7-30-22 · Comments...
Read more >eslint-config-nicestyle - npm package - Snyk
A proposal of style and rules for javascript. This config is midly strict and you can ... computed-property-spacing, error, never ... no-spaced-func, error....
Read more >eslint-config-nicestyle - npm
A proposal of style and rules for javascript. This config is midly strict and you can overwrite or add rule if you want....
Read more >SEC Proposes Narrowing Grounds for Excluding Shareholder ...
Under Rule 14a-8, a company must include an eligible shareholder's proposal in its proxy statement and bring it up for a vote at...
Read more >Coding Standards — Developer's Notebook
In order to keep the javascript code consistent, we provide ESLint rules ... First of all, have a close look at the PEP...
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 FreeTop 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
Top GitHub Comments
How about
func-call-spacing
, as I’m not sure “call” is obvious on its own?@mysticatea I think it’s better to discuss that as a separate issue