-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: fetch assets in dynamic content (#1369, #1587, #1630, #1936, #2064) #2474
base: master
Are you sure you want to change the base?
fix: fetch assets in dynamic content (#1369, #1587, #1630, #1936, #2064) #2474
Conversation
|
thanks for the contribution @mskec - looks promising! What needs to be done so this could be released @diegomura ? We also experienced this issue and are working with a nasty workaround. This fix would help us a lot! |
Hey, can you share your nasty workaround? Would be great! :) |
hej @jkergal I required to have a different header on page 1 vs page 2 and following. Instead of putting all content inside only one page element and leaving the page wraps to the page element I've added another page element. Therefore I need to separate my content between both page elements to apply different headers. |
You could try to use patch-package and apply the fix. @diegomura can you please give us some comment on this. Do you see a better way to fix this bug? |
hey @mskec maybe add a changeset and rebase to its main to make it easier for @diegomura to add this change. |
ffb096b
to
2bd2398
Compare
2bd2398
to
fadf37f
Compare
After rebasing with the latest master changes, I'm seeing errors in
|
It seems that you're missing an 'await' in the paginate function (line 263) causing it to infinitely loop until it runs out of memory:
|
Good catch @deanwyns, thank you :) |
also waiting for this fixed. just updated to 7.7.1 and noticed that my PDF was not working. problem occurs when loading images dynamically |
Hi @diegomura, can you give us some comment on this fix? Do you have concerns about the way this is fixed? I created the same PR #2240 in March 2023 and never received any feedback from you. |
I tried to patch the changes in my file but after doing so I get the following error
Did anyone get the same issue? |
I have same issue, any solution? |
I found issue on my code, check your content if it comes from API you have to check field you use in PDF file
|
Reopening PR #2240
This PR fixes crashes with images inside dynamic content.
From looking at it, the problem was that assets weren't loaded for images inside dynamic content because resolveAssets was executed before resolvePagination.
To resolve this, I've added resolveAssets as a step in relayout which forced me to add a bunch of async/await all over resolvePagination.
fixes: #1369, #1587, #1630, #1936, #2064