What is the need and use case of this feature?
My app has some observed properties / reactions that fire when the app is launched. It isn't feasible to call this code after setupPlayer() has been called because of past design considerations that are difficult to refactor. This leads to player_not_initialized rejections.
It would be great if the Android isServiceBound and iOS hasInitialized bools were exposed so my code could wait for player setup. I think there was a PR/patch for this in past versions
Describe the ideal solution
Add a public function like isPlayerSetup() which returns the related bool.
Describe alternatives you've considered
Right now, I have a wrapper function that calls getPlaybackState() and checks for the status of the promise. Returning the state of the bool seems a little cleaner.
How I can Help
I can probably work up a PR in the next month or so unless someone beats me to it.
What is the need and use case of this feature? My app has some observed properties / reactions that fire when the app is launched. It isn't feasible to call this code after
setupPlayer()
has been called because of past design considerations that are difficult to refactor. This leads to player_not_initialized rejections.It would be great if the Android isServiceBound and iOS hasInitialized bools were exposed so my code could wait for player setup. I think there was a PR/patch for this in past versions
Describe the ideal solution Add a public function like
isPlayerSetup()
which returns the related bool.Describe alternatives you've considered Right now, I have a wrapper function that calls
getPlaybackState()
and checks for the status of the promise. Returning the state of the bool seems a little cleaner.How I can Help I can probably work up a PR in the next month or so unless someone beats me to it.