Contents

# Control Couple

## Introduction

Control coupling occurs when a method or block checks the value of a parameter in order to decide which execution path to take. The offending parameter is often called a `Control Couple`.

Control Coupling is a kind of duplication, because the calling method already knows which path should be taken.

Control Coupling reduces the code's flexibility by creating a dependency between the caller and callee: any change to the possible values of the controlling parameter must be reflected on both sides of the call. A `Control Couple` also reveals a loss of simplicity: the called method probably has more than one responsibility, because it includes at least two different code paths.

You can find a good write-up regarding this problem [here](http://solnic.eu/2012/04/11/get-rid-of-that-code-smell-control-couple.html).

## Current Support in reek

`reek` warns about control coupling when:

* [Control-Parameter](Control-Parameter.md) - a method parameter or block parameter is the tested value in a conditional statement (as in the example below); or
* [Boolean-Parameter](Boolean-Parameter.md) - a method parameter is defaulted to `true` or `false`.

## Configuration

Control Couple supports the [Basic Smell Options](Basic-Smell-Options.md).

Version data entries

15 entries across 15 versions & 1 rubygems

Version	Path
reek-3.5.0	docs/Control-Couple.md
reek-3.4.1	docs/Control-Couple.md
reek-3.4.0	docs/Control-Couple.md
reek-3.3.1	docs/Control-Couple.md
reek-3.3.0	docs/Control-Couple.md
reek-3.2.1	docs/Control-Couple.md
reek-3.2	docs/Control-Couple.md
reek-3.1	docs/Control-Couple.md
reek-3.0.4	docs/Control-Couple.md
reek-3.0.3	docs/Control-Couple.md
reek-3.0.2	docs/Control-Couple.md
reek-3.0.1	docs/Control-Couple.md
reek-3.0.0	docs/Control-Couple.md
reek-2.2.1	docs/Control-Couple.md
reek-2.2.0	docs/Control-Couple.md