Allow custom mime type determination #154
Merged
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
AntonOellerer
force-pushed
the
fix/file-type-detection
branch
from
73baa48
to
c0e3afb
Compare
To allow library users to influence the file type determination process, this commit refactors the ft-detection and image dimension determination logic so that `ImageStrategy` can be filled with a custom file type detector.
AntonOellerer
force-pushed
the
fix/file-type-detection
branch
from
c0e3afb
to
f1c8dc4
Compare
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.
To allow library users to influence the file type
determination process, this commit refactors the
ft-detection and image dimension determination logic
so that
ImageStrategycan be filled with a customfile type detector.