== Why is this an issue?

include::../description.adoc[]

Code like

[source,cpp]
----
if (condition1) {
  if (condition2) {             // Noncompliant
    /* ... */
  }
}
----

will be more readable as

[source,cpp]
----
if (condition1 && condition2) { // Compliant
  /* ... */
}
----

== How to fix it

If merging the conditions seems to result in a more complex code, extracting the condition or part of it in a named function or variable is a better approach to fix readability.

=== Code examples

==== Noncompliant code example

[source,cpp]
----
if (fs::exists(path)) {
  if (fs::is_regular_file(path) || fs::is_directory(path)) { // Noncompliant
    /* ... */
  }
}
----

==== Compliant solution

[source,cpp]
----
bool isFileOrDirectory(fs::path const& path) {
  return fs::is_regular_file(path) || fs::is_directory(path);
}

/* ... */

if (fs::exists(path) && isFileOrDirectory(path)) { // Compliant
  /* ... */
}
----


ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

include::../message.adoc[]

include::../highlighting.adoc[]

'''
== Comments And Links
(visible only on this page)

include::../comments-and-links.adoc[]

endif::env-github,rspecator-view[]
