OpenapiFirst::Test 3.1.0.beta1 now raises an error when it sees a query-parameter that was not defined in the OAD.
I think this will be very useful to avoid API drift. #openapi #openapi_first

https://github.com/ahx/openapi_first

Here is a discussion how the request validation middleware should handle paths that are not defined in your #openapi API description. – Return 404 or skip the validation and pass the request to the upstream app?

Your thoughts would be very much appreciated.

https://github.com/ahx/openapi_first/issues/350

#ruby #rack #apifirst #openapi_first

openapi_first 2.7.0 was released with better support for handling multiple APIs, including an RSpec integration, and an option to adjust the request path used for validation.

https://github.com/ahx/openapi_first

#Ruby #Rack #APIfirst #openapi #openapi_first

I just released version 2.0.3 of openapi_first, which makes the test assertion method work as described and adds an option to the request validation middleware to skip the error response. This option can be useful in a code-first scenario where you want to subscribe to invalid requests / responses according to your API description.

#ruby #openapi #apifirst #openapi_first

https://github.com/ahx/openapi_first