Releases: dhleong/babbling
3.6.1
3.6.0
Enhancements:
- New queryRecommendations Channel API (#55)
- Implement API to distinguish recommended from recent (#58)
- Introduce SeriesContentListings for browsing a series' episodes (#62, #54)
- Update public Player API to improve usability (#53)
Bug Fixes and misc:
- Fix DisneyApp support (#61)
- Update disney token expiration checks (#60)
- Clean up special case query result "extras" for Prime Channel (#59)
- Migrate to auto-formatting via prettier (#52)
Notes:
This is quite a big update! There have been a bunch of (non-breaking) API updates to improve usability, like accepting an options map instead of directly accepting the onError
handler, and being able to build a Player instance without having to create a dummy ChromecastDevice
instance just to satisfy it.
The queryRecommended
API is now effectively deprecated; for most purposes, the API it provides is not terribly helpful ("somehow recommended") and was mostly implemented as a "continue watching" queue but one source might include other things. In its place is queryRecent
, which is more descriptive and also more specific, and queryRecommendations
, which lets callers specify what type of recommendations they want (or don't want). That API is definitely somewhat in flux, and not all apps support all of its features, but it should give us some room to grow.
Next, while we've had the wierd findEpisodeFor
API for a while, this release also introduces ISeriesContentListings
that is much more robust for general use. findEpisodeFor
was primarily built to support a one-off requests like "play season 1 episode 1 of " and, while that's cool, is an awful API for general use. Especially since Google Home no longer supports variable voice queries, I can't imagine that getting much use.
Instead, you can now browse a listing of all seasons of a series, and all episodes in a given season! This is much more in line with what users of a non-voice-only app might expect.
Finally, I discovered that one of the apps has been broken, probably for quite some time. It has been fixed!