Skip to content

Internal error when q is defined multiple times #511

@LucaDiba

Description

@LucaDiba

Hi team, the API returns 500 when calling GET /tracks?q=&q=foo (q defined multiple times where one time it's an empty string and another time it's not empty).

------ Previous version:
Hi team, it looks like some query parameters in GET /tracks are not considered if q is undefined.

For example, specifying the genres correctly returns only the tracks of those genres.
However, adding created_at[from] doesn't change the result and always returns the same data.

I would expect all filters to be considered even if q is not defined.

Also, note that the API returns 500 when calling GET /tracks?q=&q=foo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions