Skip to content

It is not possible to handle unknown query parameters #99

@OndrejSpanel

Description

@OndrejSpanel

Sometimes it would be handy to allow any unknown query parameters.

Motivation 1:

One of my endpoints is used for GitHub OAuth loopback. While the behavior in case of success is well documented as receiving code and state parameters, in case of error the documentation is lacking. While I have experimentally determined the parameters in such case to be error, error_description and error_uri, this is undocumented and perhaps could change anytime, causing my error handling not working as expected. Moreover. I am not really interested in some of them, but I cannot prevent them being included. At the moment I have to add them to the endpoint just to ignore them.

Motivation 2:

I am processing query parameters using request.queryParams in my endpoint, yet I have to list all possible parameter names in my endpoint signature. This contrast with subPath option available for paths. I can easily create an endpoint serving any subpath, but not any query parameters.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions