Closed danirzv closed 8 months ago
First of all, let me thank the QuestPDF.Markdown author for creating this library and actively maintaining it. You are doing an exceptional work!
I have looked at this issue and found a likely root cause. The recent QuestPDF version introduces an alternative way of specifying colors based on uint32 numbers (via the Infrastructure.Color
struct). This allows us to reduce memory usage and improve performance slightly (as the library does not need to perform string parsing or cache's key hash calculation).
It is not a breaking change from a regular application perspective, as the Infrastructure.Color
structure has an implicit string
conversion operator, and all old code should work just fine. However, this may need to be fixed with existing QuestPDF-based libraries.
My suggestion is to simply update QuestPDF.Markdown, however, I am very open to discussion and risk assessment :)
Thanks for the bug report @danirzv. And thanks for the analysis @MarcinZiabek. It sounds like an easy fix, I will look into it.
The QuestPDF 2024.3.0 is available only in the alpha version; you have around a month before this version becomes production-ready. If I am not mistaken, you only need to bump up the library version and rebuild your nuget. I am here to assist you in case any help is required :)
I've just released a pre-release version of QuestPDF.Markdown 1.8.0-alpha
that targets QuestPDF 2024.3.0-alpha
and makes use of the new Color struct. @danirzv please let me know if this version resolves the issue.
Closing due to inactivity, the provided solution should address the problem for now.
Describe the bug When updated QuestPdf from
2023.12.3
to2024.3.0-alpha
and also updated QuestPdf.Markdown from1.4.0
to1.6.1
my pdf generation started to fail which were working fine before:Environment