Skip to content

Reject non-parseable queries with 4xx #1073

@leonhandreke

Description

@leonhandreke

What I take away from #917 is that it's really hard to figure out whether your query was actually understood by yente.

We should fix this in api-v2 and just reject unparseable things with an HTTP 4xx client error

Cc @apognu another idea for the v2 API that you might have already implemented :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions