1947 a = e.behavior;
1948 }
1949 return (
1950 a.forEach(function (s, l) {1951 if (i !== s || a.length === l + 1) return t;
1952 (i = t.placement.split("-")[0]), (o = at(i));
1953 var u = t.offsets.popper,
523 }
524 };
525
526 pJS.fn.particlesUpdate = function () { 527 for (var i = 0; i < pJS.particles.array.length; i++) {
528 /* the particle */
529 var p = pJS.particles.array[i];
232
233 /* --------- pJS functions - particles ----------- */
234
235 pJS.fn.particle = function (color, opacity, position) { 236 /* size */
237 this.radius =
238 (pJS.particles.size.random ? Math.random() : 1) *
A function with high cyclomatic complexity can be hard to understand and maintain. Cyclomatic complexity is a software metric that measures the number of independent paths through a function. A higher cyclomatic complexity indicates that the function has more decision points and is more complex.
Functions with high cyclomatic complexity are more likely to have bugs and be harder to test. They may lead to reduced code maintainability and increased development time.
To reduce the cyclomatic complexity of a function, you can:
// When `cyclomatic_complexity_threshold` is set to `low`, by default it is `high`
function getCapitalCity(countryName) {
if (countryName === 'India') {
return 'New Delhi'
} else if (countryName === 'China') {
return 'Beijing'
} else if (countryName === 'France') {
return 'Paris'
} else if (countryName === 'Germany') {
return 'Berlin'
} else if (countryName === 'Italy') {
return 'Rome'
}
}
function getCapitalCity(countryName) {
const capitalCities = {
India: 'New Delhi',
China: 'Beijing',
France: 'Paris',
Germany: 'Berlin',
Italy: 'Rome'
}
return capitalCities[countryName]
}
Cyclomatic complexity threshold can be configured using the
cyclomatic_complexity_threshold
meta field in the
.deepsource.toml
config file.
Configuring this is optional. If you don't provide a value, the Analyzer will
raise issues for functions with complexity higher than the default threshold,
which is high
(only raises for issues >25) for the JavaScript Analyzer.
Here's the mapping of the risk category to the cyclomatic complexity score to help you configure this better:
Risk category | Cyclomatic complexity range | Recommended action |
---|---|---|
low | 1-5 | No action needed. |
medium | 6-15 | Review and monitor. |
high | 16-25 | Review and refactor. Recommended to add comments if the function is absolutely needed to be kept as it is. |
very-high | 26-50 | Refactor to reduce the complexity. |
critical | >50 | Must refactor this. This can make the code untestable and very difficult to understand. |