3.4.0 - Redis TLS and ACL authentication support - #4

Literal argument `true` should be passed as a named argument for clarity. >This literal is being passed positionally. Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`. Help: Consider using a named argument instead: `function_name(param: true)`.

Literal argument `true` should be passed as a named argument for clarity. >This literal is being passed positionally. Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`. Help: Consider using a named argument instead: `function_name(param: true)`.

Shell-style comments ('#') are not allowed. >This is a shell-style comment Help: Consider using double slash comments ('//') instead.

Shell-style comments ('#') are not allowed. >This is a shell-style comment Help: Consider using double slash comments ('//') instead.

Shell-style comments ('#') are not allowed. >This is a shell-style comment Help: Consider using double slash comments ('//') instead.

Call to `array_search` must enforce strict comparison. >Function `array_search` relies on loose comparison which can lead to unexpected behavior Help: Call the function `array_search` with the `$strict` parameter set to `true`.

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Avoid boolean flag parameters. >This parameter acts as a boolean flag >Boolean type declared here Boolean flags often indicate a function has more than one responsibility, making it harder to understand and test. Help: Refactor by splitting the function into two separate methods, each with a clear, descriptive name.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `elseif` clauses. >This `elseif` adds unnecessary complexity Complex conditional chains can often be simplified by using early returns or a `match` expression. Help: Refactor to use guard clauses (early returns) or a `match` expression for clarity.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.