Skip to content

Non required parameters with empty values are not caught #389

@nmeheus

Description

@nmeheus

According to the specifications an empty valued parameter is not equal to the parameter not being present. For required parameters one can use the allowEmptyValue: true/false to (dis)allow ?queryparam=, but for non required query parameters there seems no way to prevent ?queryparam= and ?queryparam(*) from passing the validation.

A small snippet to illustrate the expected behaviour, and how it fails with the current implementation: https://goplay.space/#T58uhnOPA-t

(*) Note that this behaviour (without the =) is also not working as expected for required parameters.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions