sigma67/ytmusicapi

Part of #307. Base branch: ytmusicapi-2. Read the contributor guide from #982 before starting. The mutating and action endpoints. These currently return the raw YTM response typed as JsonDict, str | JsonDict or similar, which tells a consumer nothing about what they actually got back. Scope mixins/library.py — rate_song, rate_playlist, edit_song_library_status, subscribe_artist, subscribe_artists, unsubscribe_artists, remove_history_items mixins/playlists.py — create_playlist, edit_playlist, add_playlist_items, remove_playlist_items, delete_playlist, join_collaborative_playlist mixins/uploads.py — delete_upload_entity mixins/search.py — remove_search_suggestions Watch out for Several return str | JsonDict: a plain id string on success, or the raw response. That union should become something a consumer can actually branch on. add_playlist_items returns different content depending on duplicates and whether source_playlist was used. These endpoints are the least covered by test

Part of #307. Base branch: ytmusicapi-2. Read the contributor guide from #982 before starting. The remaining browsing endpoints not covered by the core entity models. Scope mixins/browsing.py, parsed by ytmusicapi/parsers/browsing.py: get_home get_user, get_user_playlists, get_user_videos get_song, get_song_related, get_song_credits get_tasteprofile Watch out for get_home returns mixed shelf contents — songs, albums, playlists, artists in one list. parse_content_list skips renderer types it does not recognise (#970); the model must tolerate heterogeneous shelves. get_song returns the raw player response and differs from the song model in #983. Do not conflate them. get_tasteprofile returns a mapping keyed by artist name rather than a list. Definition of done All listed methods return models. mypy --strict clean.

Part of #307. Base branch: ytmusicapi-2. Read the contributor guide from #982 before starting. The hardest Phase 2 issue and the one that depends on all three core entity models. Best picked up once #983–#985 have landed and a few other Phase 2 issues have shaken out the patterns. Scope search in mixins/search.py — results across all filters: songs, videos, albums, artists, playlists, podcasts, episodes, profiles, community playlists, featured playlists, uploads get_search_suggestions, including detailed_runs=True, which currently returns list[str] | JsonList Watch out for The return type is a union discriminated by resultType. Model it so consumers can narrow on resultType and get the right fields — a single model with every field optional would defeat the point of this whole effort. scope="library" and scope="uploads" return different shapes from the default scope. ignore_spelling and the top-result shelf produce entries that differ from the regular result rows. Podcast resu

Part of #307. Base branch: ytmusicapi-2. Read the contributor guide from #982 before starting. Scope mixins/podcasts.py, parsed by ytmusicapi/parsers/podcasts.py: get_channel and get_channel_episodes get_podcast get_episode get_episodes_playlist Watch out for Episodes carry fields songs do not (date, duration, description, podcast reference) and lack several a song has, so this is likely its own model rather than a reuse of the song model from #983. Some podcast search results come back without a browseId (#976) — whatever the equivalent is here needs to be optional rather than assumed present. Definition of done All five methods return models. Tests cover an episode with and without a description. mypy --strict clean.

Part of #307. Base branch: ytmusicapi-2. Read the contributor guide from #982 before starting. Scope Read methods in mixins/playlists.py: get_playlist get_liked_songs get_saved_episodes The playlist model itself comes from #985 — this issue wires it through these three entry points and models whatever they add on top. The mutating methods in this file (create_playlist, edit_playlist, add_playlist_items, remove_playlist_items, delete_playlist, join_collaborative_playlist) are out of scope here — see #995. Watch out for get_liked_songs and get_saved_episodes are playlist responses for the special LM/SE playlists and may lack fields a normal playlist has. get_playlist(related=True) and suggestions_limit add fields to the response. Playlists containing unavailable tracks are the important edge case, and #983 should already cover it. Definition of done All three return models, including with related=True. mypy --strict clean.