/users/{user_id}/playlists isn't returning "No such user" response

[adamint]

Issue found on November 3, 2018.

Endpoint(s):

• GET /users/{user_id}/playlists

Scope(s):

• None (application is not using authentication)

Steps to reproduce:

1. Open the API Console
2. Call the get-playlists endpoint with a non-existant user-id (that is still valid) like asjdfjljaskldfkljajklsdfasdf. asjdfjljaskldfkljajklsdfasdfjfdjkjkafjkasjkfjksd and other invalid user-ids throw an error here, correctly.

Expected behaviour:

An error message like:

{
  "error": {
    "status": 404,
    "message": "Non-existant user"
  }
}

Actual behaviour:

Valid paging object that contains an empty list of tracks.

[adamint]

As I came across this, it seemed like a bug. Is there any rationale behind having this behavior?

[adamint]

any update?

[bih]

Hello @adamint,

Thanks for filing this! I can confirm I can reproduce this issue and it is indeed a bug. I'll file it with the teams after the holidays and we'll get it fixed. Cheers!