DEV Community

Cover image for Code Smell 36 - Switch/case/elseif/else/if statements
Maxi Contieri
Maxi Contieri

Posted on • Edited on • Originally published at maximilianocontieri.com

5

Code Smell 36 - Switch/case/elseif/else/if statements

First programming lesson: Control structures. Senior developer lesson: avoid them.

Problems:

  • Too many decisions together

  • Coupling

  • Duplicated code

  • Violation of Open/Closed Principle.

  • A new condition should not change the main algorithm.

  • Nulls

Solutions

  1. Polymorphism

  2. Create hierarchies/compose objects following Open closed principle.

  3. Use State pattern to model transitions.

  4. Use Strategy Pattern/Method Object to choose for branches.

Examples

  • Discrete Values

  • State transition

  • Algorithm choice.

Sample Code

Wrong

class Mp3Converter {
convertToMp3(source, mimeType) {
if(mimeType.equals("audio/mpeg")) {
this.convertMpegToMp3(source)
} else if(mimeType.equals("audio/wav")) {
this.convertWavToMp3(source)
} else if(mimeType.equals("audio/ogg")) {
this.convertOggToMp3(source)
} else if(...) {
// Lots of new clauses
}
view raw converters.js hosted with ❤ by GitHub

Right

class Mp3Converter {
convertToMp3(source, mimeType) {
const foundConverter = this.registeredConverters.
find(converter => converter.handles(mimeType));
// Do not use metaprogramming to find and iterate converters
// since this is another problem.
if (!foundConverter) {
throw new Error('No converter found for ' + mimeType);
}
foundConverter.convertToMp3(source);
}
}

Detection

Since there are valid cases for If/else usages, we should not pull the plug and forbid these instructions. We can put a ratio of if statements/other statements as a warning instead.

Relations

More info

Credits

Photo by Adarsh Kummur on Unsplash

If debugging is the process of removing software bugs, then programming must be the process of putting them in.

Edsger Dijkstra

Sentry blog image

How I fixed 20 seconds of lag for every user in just 20 minutes.

Our AI agent was running 10-20 seconds slower than it should, impacting both our own developers and our early adopters. See how I used Sentry Profiling to fix it in record time.

Read more

Top comments (3)

Collapse
 
richardsprins profile image
Richard S Prins Jr.

The code isn't at all different, not sure of the intent here?

Collapse
 
mcsee profile image
Maxi Contieri

If you see the code exactly the same is due to a bug in dev.to cache. Try refreshing the cache

Collapse
 
moopet profile image
Ben Sinclair

It's been a couple of years and it's definitely the same for me :)

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay