mulesoft/osprey-cli

Validator should reject requests with query parameters not in the RAML file

dmartinezg opened this issue · 3 comments

If a resource+method does not have query parameters defined or has some, apikit should reject requests made with query parameters not defined in the RAML file.

The expected behaviour will be:

  • If there are not query parameters defined, Osprey will accept any sent parameter
  • If there are some query parameters defined, Osprey is going to validate that only such parameters will be present

Can make it so that in strict mode, only strict adherence to the RAML is accepted?

Moved to Oprey repo.