fix: Add docxf/oform to mimetypemapping #41475
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
4 tasks
juliusknorr
requested review from
blizzz,
mejo-,
a team,
icewind1991 and
sorbaugh
and removed request for
a team
blizzz
approved these changes
Nov 15, 2023
Merged
AndyScherzinger
approved these changes
Nov 19, 2023
Signed-off-by: Julius Härtl <jus@bitgrid.net>
AndyScherzinger
force-pushed
the
bugfix/noid/docxf-oform-mimetype
branch
from
b5ccc7b to
cd6c192
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.
Other parts were already added with #32481 however the mimetype detection for files uploaded relies on the mimetypemapping.dist.json list.
Upload on master for those files is still blocked by nextcloud-libraries/nextcloud-upload#956 nextcloud-libraries/nextcloud-upload#955
Steps to reproduce:
Example file: New form template.docxf.zip