Externalize custom mime types configuration for storage providers #2613
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
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
glpatcern
force-pushed
the
mimetypes-config
branch
4 times, most recently
from
abcf49c
to
4329c49
Compare
glpatcern
force-pushed
the
mimetypes-config
branch
from
4329c49
to
9550f67
Compare
ishank011
reviewed
Mar 7, 2022
ishank011
approved these changes
Mar 7, 2022
Daniel-WWU-IT
pushed a commit
to Daniel-WWU-IT/reva
that referenced
this pull request
Mar 16, 2022
45 tasks
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.
As discussed with @ishank011 this small PR moves the custom mime types configuration to a JSON file, so that it can be reused when many storage providers are deployed at the same time.