Fix XMLTV proxy routing issue and Xtream Codes VOD data handling #176
+668
−54
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
The IPTV provider returned data seems to be partially complete, or missing pieces that this proxy is expecting. The unmarshalling processes was failing mainly when the 'info', 'video' & 'audio' JSON data portions were empty or missing. These fields now have their own unmarshalling methods and if an error is encountered during this process, then it attempts to unmarshall the fields individually in the hope of returning as much data as possible. If additional errors occur these should now be logged.
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.
This update fixes the incorrectly routed XMLTV links for EPG data and addresses an issue with Xtream Codes VOD (Shows & Movies), where the IPTV provider returned incomplete or missing data that the proxy expected.
Thanks to @jtdevops for the fix!
See issue #155 for more details.