Debug ul error

[jbennie]

v1.1.0 fails when used with QuestPDF 2023.12.5 when encountering UL tags in the data.
Investigation of the breaks suggested they are due to changes to ListsContainer Types in QuestPDF.

On upgrade of QuestPDF to (2023.12.5) the following fixes were also applied.

• Unit type has a name change for Mill to Mil
• Depreciated Image(img, scale) function in ImgComponent replaced with Image(img).FitArea() to achieve the equivalent Effect.
• Added CommunityLicense to the Example project: 2023.12.5 requires a licence definition.
• Added a AlignCenter() to the ImgComponent to improve default output aesthetics.

[mjefim]

I would really need this fix, is there any way to help the process of a release?

[MarcinZiabek]

@jbennie Would you please share more details of how the generation process fails after upgrading to the latest QuestPDF version? Maybe I will be able to help somehow - having exception messages and screenshots would be fantastic 😄

[jbennie]

It unfortunately fails silently. There are multiple causes of failure which. They are listed on my pr notes. its very easy to observe the problem, just update  QuestPdf to version 2023.12 .5 (of the top of my head its the latest)build and run with very simple html that includes a ul li fragment. the immediate problem is the type change in Unit Definition.   I can expand further if needed after you’ve had a look at the pr diffs Sent from my iPhoneOn 22 Feb 2024, at 09:13, Marcin Ziąbek @.***> wrote: @jbennie Would you please share more details of how the generation process fails after upgrading to the latest QuestPDF version? Maybe I will be able to help somehow - having exception messages and screenshots would be fantastic 😄

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[sebbii17]

Any news on this?