Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:mirador_crash #3927
base: main
Are you sure you want to change the base?
fix:mirador_crash #3927
Changes from 6 commits
3f2a803
f5d8cf2
23c6285
b3c5812
22c713b
13c7a4a
c095751
5595b44
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I should have noticed this earlier: This change results in a list of errors in the catalog list for every manifest that is configured in the
catalog
settings but not inwindows
. While you can "Try again" successfully, this should be fixed. It's probably sufficient to change this line toManifests that have not been used in windows before don't have a manifesto instance up until this point, and at the moment the component is initially rendered,
isFetching
is not yet true, so the same check that is used forready
should be used here additionally.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.
I'm also thinking about how to test this automatically, no efficient idea yet, but I think it's not necessary for the scope of that PR.