Refactoring (creating invoices, generating pdf files, sending emails) #398
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
UPGRADE FROM 2.2 TO 3.0
Depend on: #395 PR
Changes
Invoice:Invoicenewpathfield (unique) storing the final PDF location (e.g. annually/2025_10_000000001.pdf).InvoiceCreatortoInvoiceFactory.InvoiceCreatorno longer generates PDFs at creation time.PDFs are generated on first provide/download via the provider.
InvoiceFactorynow depends onInvoiceFileNameGeneratorInterface.On creation, it calls:
and passes it to the
Invoiceconstructor as$path.InvoiceFileProvideris now the primary orchestrator of PDF generationRemoved
InvoiceFileNameGeneratorInterfacefromInvoiceFileProvider.Added
sylius_invoicing.pdf_generator.enabledparameter to constructor.InvoiceFileNameGeneratorsignature & scopingBC break:
generateForPdf()now accepts string $invoiceNumber (notInvoiceInterface).SYLIUS_INVOICING_SEQUENCE_SCOPE:InvoicePdfFileGeneratorsimplified:Removed dependency on InvoiceFileNameGeneratorInterface.
Uses
Invoice::path()as the filename: