Klastic
commented
7 months ago The issue with our API endpoint for track lookups by name, which previously did not include artist information in the response, has now been successfully resolved. Our API now returns artist details along with the track information, addressing the problem of incorrect track retrieval when multiple tracks share the same name. This enhancement ensures users can accurately identify and access tracks, especially in cases where different artists have songs with identical titles.
However, it's important to note that some pages may still experience issues due to a separate, ongoing problem detailed in Issue #43. This issue is currently being addressed, and we are working diligently to resolve it as quickly as possible to prevent any further impact on user experience.
Description
Our current API endpoint for looking up tracks by name does not include artist information in the response. This limitation becomes problematic when multiple tracks share the same name, as the endpoint fetches and returns the first matching track without considering the artist. This behavior can lead to incorrect track retrieval and confusion, especially in cases where songs with the same name exist by different artists.
Steps to Reproduce
Expected Behavior
The API endpoint for track lookup by name should be enhanced to include artist information in its response. Ideally, it should allow for filtering by artist name to accurately retrieve and return the correct track when multiple tracks share the same name.
Actual Behavior
The API endpoint currently returns only the first track match found by name, without accounting for the artist, leading to potential mismatches and inaccuracies in track retrieval.
Proposed Changes
Environment
Additional Context
This enhancement is crucial for improving the functionality and reliability of our track lookup API. By incorporating artist information and allowing for artist-specific queries, we can significantly improve the accuracy of track retrieval, enhancing the user experience for developers and end-users interacting with our API.
Resolving this issue will require updates to both the API's logic and its documentation to reflect these new capabilities. We aim to implement these changes promptly to minimize any disruptions and maximize the benefits of this improvement.