You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FPDI, whose class extends FPDF, does not declare the FDPF library as a requirement in its composer.json. Its official documentation says to require both libraries alongside each other like below.
Expected Mozart/PSR_04/setasign/Fpdi/FpdfTpl.php (line 18) to extend \Mozart_FPDF but it still just extends \FPDF.
While the correct place to fix this would normally be in the FPDI repo, I'm posting here in the hope there is a way to define a package inside my own composer.json in a way that Mozart would handle this. The lack of FPDF requirement is by design in FPDI:
FPDI is ... in FPDF. Because it is also possible to use FPDI with TCPDF, there are no fixed dependencies defined.
Changing to the following results in FPDF being installed to vendor, but not processed by Mozart.
FPDI, whose class extends FPDF, does not declare the FDPF library as a requirement in its composer.json. Its official documentation says to require both libraries alongside each other like below.
Expected
Mozart/PSR_04/setasign/Fpdi/FpdfTpl.php
(line 18) to extend\Mozart_FPDF
but it still just extends\FPDF
.While the correct place to fix this would normally be in the FPDI repo, I'm posting here in the hope there is a way to define a package inside my own composer.json in a way that Mozart would handle this. The lack of FPDF requirement is by design in FPDI:
Changing to the following results in FPDF being installed to vendor, but not processed by Mozart.
The text was updated successfully, but these errors were encountered: