You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We update patches automatically in our projects, since we expect them to be backwards compatible and not require us to do manual changes.
However, #2247 was released as a patch, even though it requires users of the previous usePDF hook manual changes that are not mentioned anywhere.
If I run that with the current change, I still get an error response:
An error occurred while loading the PDF.
PDF.js v3.6.126 (build: 3f89a99a5)
Message: Invalid page request.
All that said, it is not relevant for me at least, that this previous approach is still usable, but rather some notice and documentation on how to adjust, if you're experiencing issues with it, might be sufficient.
Describe the bug
We update patches automatically in our projects, since we expect them to be backwards compatible and not require us to do manual changes.
However, #2247 was released as a patch, even though it requires users of the previous
usePDF
hook manual changes that are not mentioned anywhere.To Reproduce
Previous usage (based on test in #2247):
New usage:
Expected behavior
Backwards compatibility on a
patch
or release as aminor
or evenmajor
version, which mentions required changes for affected users.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: