Another JS Switch Trick

#javascript #coding #programming

[@FunctionGermany]

breaks principle of least surprise, therefore i would not recommend this.

[@apidas]

ah you must be fun to work with 😂

[@gordonfreimann]

have you forgotten to take your meds again?

[@FunctionGermany]

@@apidas when production is down and i need to fix a bug fast i don't want to run into "fun" code.

[@TylerJBrown192]

1000% agree. While this method of utilizing a switch _could_ result in less overall LOC due to not needing curly braces for an if statement declaration, it is inherently less extensible as sequential if/else statements.
This is something I'd look at in a codebase, and after 10 seconds go "huh okay, cool I guess", and move on with my day very slightly annoyed that I had to spend those 10 seconds processing the deviation in standards haha

[@apidas]

@@FunctionGermanyyeah, keep your for loop and require statements

[@BoonBoonitube]

C# has much more flexible switch statements, since I regularly use both C# and JS, this trick goes a ways into making JS switches as flexible as in C#

[@offroaders123]

Discovered this recently too, it works really well for some instances! I haven't had much experience in Rust, but I heard the match statement kind of works like this. It would be great to have it in JS too!

[@dinckelman]

I had no idea you can do that!

[@real_ouss]

Just use an if statement dude 😂

[@dellavita3463]

😂 that’s what I thought

[@les2997]

It might be a little neater than if then else, but not by much

[@Shizzymynizzy]

Very cool

[@idontwhy3132]

neat

[@Tarabass]

Smelly code

[@ChaimMosheStern]

Or you can just do if else

[@lucas.codes.tutorials]

This is not as performative as an if-else chain because every time it is executed, the interpreter will execute the pointless comparison "true==true", so besides the comparisons executed on each case, an extra unnecessary comparison will be executed