A couple of questions

Question

A couple of questions

ceresti-mrw opened this issue 7 years ago · comments

Is there a reason that the /me/videos call is not supported?
Is there a reason why not all of the JSON returned it put into the Video struct?

Dmitriy Sokolov · Answer 1 · Thu Aug 24 2017 03:32:45 GMT+0800 (China Standard Time)

Is there a reason that the /me/videos call is not supported?

I put this in the documentation here and here. And take a look at the code. Sorry, the description of the methods is pretty meager, but I'm working on it!

Is there a reason why not all of the JSON returned it put into the Video struct?

What do you have in mind? One of the fields is missing?

ceresti-mrw · Answer 2 · Thu Aug 24 2017 04:32:45 GMT+0800 (China Standard Time)

Thanks for responding so quickly. My bad, I did not see the ‘Me’ documentation. I do need access to the ‘File’ subtree of the JSON response. I’ve just added this in the fork I created and am now testing it. It would be great if it came directly from your version. Mark

…

On Aug 23, 2017, 12:32 PM -0700, Dmitriy Sokolov ***@***.***>, wrote: > Is there a reason that the /me/videos call is not supported? I put this in the documentation here and here. And take a look at the code. Sorry, the description of the methods is pretty meager, but I'm working on it! > Is there a reason why not all of the JSON returned it put into the Video struct? What do you have in mind? One of the fields is missing? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Dmitriy Sokolov · Answer 3 · Thu Aug 24 2017 16:07:56 GMT+0800 (China Standard Time)

Well ... i waiting commit in your fork (or PR)

ceresti-mrw · Answer 4 · Fri Aug 25 2017 00:02:31 GMT+0800 (China Standard Time)

Sorry … I didn’t understand that you were waiting. I’ll get that out today.

…

On Aug 24, 2017, 1:07 AM -0700, Dmitriy Sokolov ***@***.***>, wrote: Well ... i waiting commit/PR in your fork — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.