feat(YOUTUBE PLAYER): Expose private _player object

[mattiLeBlanc]

Feature Description

Please expose the private _player object because we can use that to access things like getPlaylist() or getVideoData which comes in handy.

Use Case

I want to control the youtube playlist myself and not use the build in controls in the iframe due to usability issue on TV.
Therefor, i can get official access to the _player I can get the playlists ids and load a next video or tell the player to execute nextVideo.

[crisbeto]

I think it's valid, but the problem is that the player isn't necessarily always available. E.g. we haven't initialized it when showing the placeholder or if you try to read it while the API is loading.

[mattiLeBlanc]

@crisbeto I understand.
The only way I can use it now is to reference and put // @ts-ignore above it. Which is not great.
Maybe you can make it available with a side note that is may be undefined in certain cases.
I would be using it when a video or playlist is loaded.

[mattiLeBlanc]

@crisbeto actually I found another way which may work (and could be documented)

onReady(event: YT.PlayerEvent) {
    console.log('event', event.target.getPlaylist())
}

html:

<youtube-player
      [videoId]="source.reference"
      [height]="height()"
      [width]="width()"
      (stateChange)="stateChange($event)"
      (ready)="onReady($event)"
      ....

I can now use the event.target which is Player reference and it is fully typed. So that works for me as a workaround for now.
But It would be great if the player becomes public, so I can execute player.nextVideo or previousVideo.

Strangely this event doesn't fire if you only load 1 video instead of a playlist. I guess that is an implementation inconsistence in this library?

[crisbeto]

Yeah that is likely due to YouTube's API. I'm closing this, because exposing the player will provide multiple sources of truth for the component and will complicate our setup where we buffer the commands if the user tries to interact with the player before it has loaded.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}