-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend file type support #72
Open
Rubo3
wants to merge
1
commit into
sheldonkwoodward:release/1.0.9
Choose a base branch
from
Rubo3:patch-3
base: release/1.0.9
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that the
info['container']['recognized']
check belongs to theverify_matroska
function, so we can reuse it in other checks down the road. And in that case, I think we would still need to use theverify_matroska
check here since we are "importing" a file.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is used in
verify_recognized
, but I thought that check here is not enough, the file must also be supported, hence theand info['container']['supported'] is True
. I removedverify_matroska
because I found your package can work with file types other than MKV (I have tested it with MP4, but ideally it should work with the other supported file types, too) and then produce an MKV, and I wouldn't call theverify_supported
because we already have the JSON dictionary, we can query it directly.I also find the code in
Verifications.py
to be rather duplicated, and I think theinfo
dictionary could be useful to other users, so I have come up with this, a new functionidentify_file
(or maybe justidentify
) which does the heavy lifting forverify_matroska
,verify_recognized
andverify_supported
:I have removed the
verify_mkvmerge
check because I think it is not necessary here, the user can check it when they need, before using other functions which depend onmkvmerge
, instead of having the package check it every time. (I have also not updated the documentation.)What do you think?