It looks like we currently return an HTTP/400 error when a user is not found in an API call. Shouldn't this be a 404? (I could maybe see arguing for a 403, but 400 seems wrong here considering the only thing the client did "wrong" was asking for a user that doesn't exist).
It looks like we currently return an HTTP/400 error when a user is not found in an API call. Shouldn't this be a 404? (I could maybe see arguing for a 403, but 400 seems wrong here considering the only thing the client did "wrong" was asking for a user that doesn't exist).
NOTE: If we do fix this, we need to make sure @sublinks/sublinks-frontend-service is aware since they might need to update the seeder