build(deps): bump tecnickcom/tcpdf from 6.11.3 to 7.0.2#4454
Closed
dependabot[bot] wants to merge 1 commit into
Closed
build(deps): bump tecnickcom/tcpdf from 6.11.3 to 7.0.2#4454dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Annotations
3 errors, 10 warnings, and 3 notices
|
Run Mago
Process completed with exit code 1.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfEngine.php#L47
Could not infer a precise return type for function `phpMyFAQ\Export\Pdf\Engine\TcpdfEngine::output`. Saw type `mixed`.
>Type inferred as `mixed` here.
The analysis could not determine a specific type for the value returned here, resulting in `mixed`. This can happen with complex code paths or unannotated data.
Help: Add specific type hints to variables, parameters, or properties involved in calculating the return value. Consider adding a specific return type declaration to the function signature to catch potential mismatches earlier.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L64
Property `$TextColor` does not exist on class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`.
>Property not found here
>On instance of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
The class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument` does not define the property `$TextColor`.
Help: Define the property in the class or check for its existence before accessing it.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #9 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$resize` but parent `TCPDF::image()` names it `$_resize`
>Parameter named `$resize` but parent uses `$_resize`
>Parent method `TCPDF::image()` parameter `$_resize` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_resize` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #8 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$align` but parent `TCPDF::image()` names it `$_align`
>Parameter named `$align` but parent uses `$_align`
>Parent method `TCPDF::image()` parameter `$_align` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_align` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #7 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$link` but parent `TCPDF::image()` names it `$_link`
>Parameter named `$link` but parent uses `$_link`
>Parent method `TCPDF::image()` parameter `$_link` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_link` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #6 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$type` but parent `TCPDF::image()` names it `$_type`
>Parameter named `$type` but parent uses `$_type`
>Parent method `TCPDF::image()` parameter `$_type` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_type` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #5 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$h` but parent `TCPDF::image()` names it `$_h`
>Parameter named `$h` but parent uses `$_h`
>Parent method `TCPDF::image()` parameter `$_h` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_h` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #4 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$w` but parent `TCPDF::image()` names it `$_w`
>Parameter named `$w` but parent uses `$_w`
>Parent method `TCPDF::image()` parameter `$_w` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_w` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #3 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$y` but parent `TCPDF::image()` names it `$_y`
>Parameter named `$y` but parent uses `$_y`
>Parent method `TCPDF::image()` parameter `$_y` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_y` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #2 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$x` but parent `TCPDF::image()` names it `$_x`
>Parameter named `$x` but parent uses `$_x`
>Parent method `TCPDF::image()` parameter `$_x` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_x` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Export/Pdf/Engine/TcpdfDocument.php#L85
Parameter #1 of `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument::image()` is named `$file` but parent `TCPDF::image()` names it `$_file`
>Parameter named `$file` but parent uses `$_file`
>Parent method `TCPDF::image()` parameter `$_file` defined here
>In class `phpMyFAQ\Export\Pdf\Engine\TcpdfDocument`
Parameter name changes can break code using named arguments.
Help: Consider renaming the parameter to `$_file` to match the parent method.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Category/Language/CategoryLanguageService.php#L80
Assigning `mixed` type to a variable may lead to unexpected behavior.
>Assigning `mixed` type here.
Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type.
Help: Consider using a more specific type to avoid potential issues.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Category/Language/CategoryLanguageService.php#L85
Redundant condition: variable `$row` (type `stdClass`) is already known to be `empty-countable`.
>This condition always evaluates to true
The type of variable `$row` (type `stdClass`) already satisfies the condition that it is `empty-countable`. This check is redundant.
Help: This condition is always true and the associated code block will always execute if reached. Consider simplifying.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Category/Language/CategoryLanguageService.php#L85
Redundant `||` operation: left operand is evaluated and right operand is always falsy.
>Left operand is evaluated
>Right operand is always falsy
The `||` operator will always return the boolean value of the left-hand side in this case.
Help: Consider simplifying this expression to just the left operand.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Category/Language/CategoryLanguageService.php#L85
Redundant `===` comparison: left-hand side is never identical to right-hand side.
>Left operand is `stdClass`
>Right operand is `array{}`
The `===` operator will always return `false` in this case.
Help: Consider simplifying or removing this comparison as it always evaluates to `false`.
|
background
wait
wait-all
cancel
parallel
Loading