Nested Ternaries are Great

Eric Elliott
Jan 25, 2018 · 6 min read
Image for post
Image for post
Smoke Art Cubes to Smoke — MattysFlicks — (CC BY 2.0)

Conventional wisdom is sometimes unwise.

(conditional)
? truthyClause
: falsyClause

Expressions vs Statements

Familiarity Bias

const withIf = ({
conditionA, conditionB
}) => {
if (conditionA) {
if (conditionB) {
return valueA;
}
return valueB;
}
return valueC;
};
const withTernary = ({
conditionA, conditionB
}) => (
(!conditionA)
? valueC
: (conditionB)
? valueA
: valueB
);

Daisy Chaining vs Nesting

const withIf = ({
conditionA, conditionB
}) => {
if (!conditionA) return valueC;
if (conditionB) {
return valueA;
}
return valueB;
};

Syntax Clutter

Less code = less surface area for bugs = fewer bugs.

Side Effects and Shared Mutable State

Using ternaries will make you a better developer.

Conclusion

Learn More at EricElliottJS.com

Image for post
Image for post

JavaScript Scene

JavaScript, software leadership, software development, and…

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store