Can’t tell from a glance if tabs or spaces so hard to tell 
The following code is... switch (type) { case SELECTED: const current = 'a' // ... other code then return case UN_SELECTED: const current = 'b' // ... other code then return }
-
-
-
Always spaces... always
Kraj razgovora
Novi razgovor -
-
-
I'm just gonna leave this here:https://eslint.org/docs/rules/no-case-declarations …
-
I'm just going to leave this here:https://twitter.com/HenrikJoreteg/status/1222639426863415297?s=20 …
The "const" in the first case is not scoped to just that case statement. So the first const is already available in the second case. Solutions: 1. Add curly statements to case to create a block scope (lint rules exist for this). 2. Don't use switch (aka, the Python solution
)Prikaži ovu nit - Još 1 odgovor
Novi razgovor -
-
-
This is why I always wrap multiline case sections in braces (anonymous blocks)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
"Not fine" in that it doesn't work but "fine" as in I wish it did.
- Još 7 drugih odgovora
Novi razgovor -
-
-
Needs curly brackets to scope `const current`
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Without checking, not sure if `const` will be block scoped without curly bracket to be honest…
-
Const is always block scoped, but without the curlies, the block nearest block is not inside the case.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.