tidal: `search_limit` is ignored

[snejus]

Problem

The Tidal plugin does not appear to honor tidal.search_limit. With a config such as:

tidal:
  search_limit: 1

Tidal album and track searches still return (at least 20+) results.

Expected behavior

Tidal should cap album and track search candidates using the configured search_limit, matching the behavior of other metadata source plugins.

Likely cause

Tidal implements candidates() and item_candidates() directly, then calls api.search_results() from search_albums_by_query() and search_tracks_by_query(). That bypasses the shared search path that reads search_limit into SearchParams.limit.

Suggested fix

Thread search_limit through the Tidal query search path, or truncate returned Tidal relationships before resolving album/track IDs. Add focused tests for both album and track search with search_limit: 1.

Tagging @semohr for visibility.

[Mo200227]

Hi, I'd love to take a stab at this one! I'll look into threading search_limit through the Tidal search path or truncating results. Will update here if I have questions

[kveni12]

Hi! I'd like to take a stab at this. Plan: thread search_limit through the Tidal query search path so it's read and applied in search_albums_by_query() and search_tracks_by_query(), and add focused tests for both album and track search with search_limit: 1.