Nullable check of java:S2259 does not respect optional code flow

Sonarqube 9.7.1

    var foo= Optional.ofNullable(fooValidatable) // this is the trigger to guess fooValidatable could be null
                                          .map(Validatable::getValue)
                                          .orElse(Boolean.FALSE); // or else and early exit not respected in code flow analysis

    if (foo.equals(Boolean.FALSE)) {
      // not enabled so ok
      return true;
    } else  {
      fooValidatable.addDistinctError(new ValidationMessage()); // here sonar thinks fooValidatable is nullable
      return false;
    }

As described in the comments the code flow that sonar tries to construct for nullable access can not happen because the orElse use on Optional.

Same when using checks on Optional for isPresent or isEmpty, its not considered by the rule producing hundreds of false positives!!

Kind regards,
Michael