You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And I'd love a way to do something like: movie.streams.audios or something and have it return these two entries in an array of two objects of audio class or something to that effect:
Note that audio is streamType="2" so that should be pretty straight forward, however I was thinking about how to implement this and it would make sense to break each stream type out into its own class, but herein lies the problem. streamType="1" is video and there is already a Video class, so I'm not sure how to go about doing this. What are the thoughts on the best way to tackle this?
Would it be best to leave video out of it and just do audio and subtitles? Or would it be best to name them like StreamVideo, StreamAudio, and StreamSubtitle, though that seems a bit awkward and not super discoverable.
The text was updated successfully, but these errors were encountered:
Add better support for accessing stream types, like video, audio, and subtitles.
For example on this movie the streams section of the XML looks like this:
And I'd love a way to do something like:
movie.streams.audios
or something and have it return these two entries in an array of two objects of audio class or something to that effect:Note that audio is
streamType="2"
so that should be pretty straight forward, however I was thinking about how to implement this and it would make sense to break each stream type out into its own class, but herein lies the problem.streamType="1"
is video and there is already aVideo
class, so I'm not sure how to go about doing this. What are the thoughts on the best way to tackle this?Would it be best to leave video out of it and just do audio and subtitles? Or would it be best to name them like
StreamVideo
,StreamAudio
, andStreamSubtitle
, though that seems a bit awkward and not super discoverable.The text was updated successfully, but these errors were encountered: