Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unexpected token in PHPDoc type >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Unexpected token in PHPDoc type >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Docblock type mismatch for variable `$data`. >This docblock asserts the type should be `array<array-key, mixed>`, but it was previously defined as `object`. The type of the variable defined in the docblock does not match the previously defined type. Help: Change the docblock type to match `object`, or update the variable definition to a compatible type `array<array-key, mixed>`.

Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unclosed inline tag >This part of the docblock has a syntax error >The error is within this docblock >This docblock is associated with the following statement An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4.1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Cannot perform array access on value of type `int`. >The expression might be `int` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `object`. >The expression might be `object` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `bool`. >The expression might be `bool` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `bool`. >The expression might be `bool` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `bool`. >The expression might be `bool` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `object`. >The expression might be `object` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `int`. >The expression might be `int` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `object`. >The expression might be `object` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `int`. >The expression might be `int` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Cannot perform array access on value of type `int`. >The expression might be `int` here. Attempting to use a scalar value as an array will result in a runtime error. Help: Ensure the variable holds an array before accessing it.

Loop is unconditionally terminated and will not iterate. >This loop will only execute once at most >The loop is exited by this unconditional `return` statement Loops that do not iterate are often misleading and can indicate a logic error or redundant code. Help: Consider refactoring the code. If the loop is intended to run only once, an `if` statement might be clearer.

Loop is unconditionally terminated and will not iterate. >This loop will only execute once at most >The loop is exited by this unconditional `break` statement Loops that do not iterate are often misleading and can indicate a logic error or redundant code. Help: Consider refactoring the code. If the loop is intended to run only once, an `if` statement might be clearer.

Unclosed inline tag An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unexpected token in PHPDoc type This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Unexpected token in PHPDoc type This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Unexpected token in PHPDoc type This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Unclosed inline tag An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unexpected token in PHPDoc type This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Unclosed inline tag An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.

Unexpected token in PHPDoc type This token cannot appear here, so the type or tag stops making sense at this point. Help: Remove the stray token, or fix the type or tag syntax leading up to it.

Unclosed inline tag An inline tag such as `{@see Foo}` was opened with `{` but never closed. Help: Add the closing `}` that ends the inline tag.