Fix remote embedding RIFF when specifying mime type #551
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
ok-nick
force-pushed
the
ok-nick/remote-riff
branch
from
e8aeb50 to
4af9684
Compare
3 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.
Changes in this pull request
When signing a remote manifest into a RIFF file and specifying a mime type (such as one derived from
crate::format_from_path), RIFF will error withUnsupportedType. Currently, RIFF explicitly checks if the format passed was an extension (not mime type as well). We can either add the mime types to this check or remove the check completely (since all supported formats are handled the same anyways).Checklist
TO DOitems (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.