Import mandatory query parameters as query rather than in the URL template
When an API is imported into API-M using Swagger, mandatory query parameters are imported into the URL template rather than as query parameters.
The effect of this is when a parameter is missing API-M returns a 404. The correct behaviour should be to return a 400 Bad Request with a validation error, or pass the request to the back-end API to return an appropriate error.
I suggest adding an option to import mandatory query parameters from Swagger as query parameters.
Gustav Sinder commented
This is very confusing to API consumers. It ought be configurable to leave the validation to the backend service instead.
Baiyuan Wang commented
Is there any update? it's really a critical feature
Adrien Dorsaz commented
I've seen the same behavior with the WADL files.