Add detailed error logging for HTML/PDF generation failures

[Copilot]

When Razor view rendering or PDF generation fails, exceptions are swallowed with no context about what went wrong or what HTML was produced. This makes diagnosing template/data issues very difficult.

Changes

ViewRenderService

• Injected ILogger<ViewRenderService>
• Wrapped RenderAsync in try/catch; on failure logs the view path and any partial HTML already written to the buffer before re-throwing

HtmlToPdfService

• Injected ILogger<HtmlToPdfService>
• Wrapped Document.ParseDocument / SaveAsPDF in try/catch for both PrintOrdersToPdf and PrintPackagingSlipsToPdf; on failure logs the full HTML passed to Scryber before re-throwing

catch (Exception ex)
{
    _logger.LogError(ex, "Error generating PDF from order HTML. HTML content: {Html}", html);
    throw;
}

Note: Logging full HTML at Error level will include order/shipment data (names, addresses). This only fires on actual failures — consider truncating if that's a concern in your production log retention policy.

[Copilot]

Pull request overview

Adds structured error logging around Razor view rendering and Scryber PDF generation to improve diagnosability when HTML/PDF output generation fails.

Changes:

• Injected ILogger<ViewRenderService> and logs view path + partial rendered HTML on RenderAsync failures.
• Injected ILogger<HtmlToPdfService> and logs HTML payload when Document.ParseDocument / SaveAsPDF fails for order and shipment PDFs.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
src/Web/Grand.Web.Common/ViewRender/ViewRenderService.cs	Adds logger injection and logs partial HTML output when view rendering throws.
src/Business/Grand.Business.Common/Services/Pdf/HtmlToPdfService.cs	Adds logger injection and logs HTML input when Scryber parse/PDF save throws (orders + shipments).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.