Rule proposal: `empty-brace-space`
See original GitHub issueThis rule would enforce spaces between braces in empty anonymous functions and try/catch braces. It is important because it is a syntax style I need to follow but isn’t automatically caught by xo already.
Fail
try { } catch { }
() => { }
Pass
try {} catch {}
() => {}
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:12 (5 by maintainers)
Top Results From Across the Web
SEC Proposes Amendments to Modernize Shareholder ...
The Securities and Exchange Commission today proposed amendments to Exchange Act Rule 14a-8, the shareholder-proposal rule, which requires ...
Read more >CFOs will be at the center of climate-risk disclosure reporting ...
Persefoni's Kristina Wyatt predicts the SEC's climate-disclosure rule will go into effect early next year.
Read more >Full article: Race, Space, and the Regulation of Surplus Labor
This essay examines the joint racial and class domination exercised in Los Angeles's Skid Row. Known widely as the “homeless capital of the ......
Read more >Volcker rule may disadvantage U.S. banks: OCC's Walsh
The Volcker rule's restrictions on proprietary trading and hedge fund ... to craft a clear proposal, as required by the 2010 Dodd-Frank law....
Read more >Environmental, Social and Governance Report
At Rackspace Technology®, we're committed to helping companies around the ... governance topics, including compliance with laws, rules and regulations;.
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
To
for (;;) {}
. This rule should only be about “brace space”. Nothing else.i get this error but when I correct it, vs-code automatically injects a space back in when I save. Anyone know what rule is doing this?