Treat region parameters that cover the entire image as 'full' in Orchestrator #800
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
griffri
force-pushed
the
feature/iiif_detect_full_image
branch
from
25e923f
to
c4d6e3d
Compare
…uestFullOrEquivalent
…ll_WithNoMatchingThumbs test, refactor ImageRequestHandler changes,
JackLewis-digirati
approved these changes
Apr 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #781
This PR updates
ImageRequestHandlerto treat IIIF image requests that request a region covering the entire image (e.g0,0,512,512for a 512x512 image) asfull. It also includes tests that verify this behaviour.