-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closes #10965; fix resolve redirect chain in export #11038
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
Closes #10965; fix resolve redirect chain in export #11038
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes an issue where redirect chains were not being properly resolved during export operations. The problem occurred when infogami returned a redirect type object instead of a hydrated Work object, causing the export to fail with Nothing being returned.
- Replaces the incorrect method call on the redirect object with proper static method usage
- Imports the
Workclass to access the correctresolve_redirect_chainmethod - Ensures the resolved work key is properly retrieved and used to fetch the actual work object
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm! Tested on prod and my reading log works now 👍 Re-assigning to me since Mek and I were chatting about it.
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Closes #10965
Technical
The
workwe were getting back from infogami was actually a typeredirectand was not hydrated by the core.models.Work class (and returnedNothing).Stakeholders
@cdrini