Added support for EXTTV and keeping of custom tags #209
Conversation
This file contains hidden or 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
This commit: - Adds support for `EXTV`: I haven't found any official specification on the format, but seems to be used throughout the web. - Add support for keeping custom tags on the lists. This means it's now possible to do a `load()` / `dumps()` cycle without loosing any metadata.
Contributor
|
Hello @bokysan thank you for the contribution. |
Author
|
Here's info from Google. Basically additional info for IPTV channels. Namely, the structure seems to be as follows: So:
|
Contributor
|
@mauricioabreu isn't the case of custom parser usage instead of code here? |
Contributor
|
@leandromoreira I am not sure if it will work. I will try to achieve the same goal of this PR by using the custom parser. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This commit:
EXTV: I haven't found any official specification on the format, but seems to be used throughout the web.load()/dumps()cycle without losing any metadata.