Skip to content
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

Youtube PlaylistItemSnippet doesn't have ts definition for 'videoOwnerChannelId' and 'videoOwnerChannelTitle'. #2574

Closed
metamon123 opened this issue Mar 27, 2021 · 1 comment · Fixed by #2575
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@metamon123
Copy link

Pre-check

  1. Is this a client library issue or a product issue?
    It's client library issue.

  2. Did someone already solve this?
    I couldn't find related issues about missing definition of 'videoOwner*' in both StackOverflow and issue list for this repository.

  3. Do you have a support contract?
    No. This is just an personal report.


Statement

Below fields

  • videoOwnerChannelId
  • videoOwnerChannelTitle

are not defined in Schema$PlaylistItemSnippet interface (ts) although


Environment details

  • OS: Windows 10
  • Node.js version: v12.13.1
  • npm version: 6.12.1
  • googleapis version: 59.0.0

Steps to reproduce

  1. Send PlaylistItems.list API request
import * as google from 'googleapis';
const youtube = new google.youtube_v3.Youtube({ auth: client /* Your OAuth2Client client */ });
const res = await youtube.playlistItems.list({
  '<any-playlist-id>',
  part: ['snippet'],
});

console.log(res.data.items[0].snippet['videoOwnerChannelId'], res.data.items[0].snippet['videoOwnerChannelTitle']);
  1. Check response. It contains videoOwnerChannelTitle and videoOwnerChannelId as official youtube playlistItems api docs specifies.

p.s. Since this is my first issue raising in open source environment, I'm not sure I have followed reporting procedure correctly.
Please feel free to tell me if I made any mistake!

@JustinBeckwith JustinBeckwith added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Mar 27, 2021
@JustinBeckwith JustinBeckwith self-assigned this Mar 27, 2021
@JustinBeckwith
Copy link
Contributor

👋 thanks for reporting this! This is a real bug. We have a fix coming, but it's probably going to be monday until it gets out. Apologies!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants