Use Rack::MockRequest for correct router recognize on hanami app

[AlexeyMatskevich]

This should fix hanami/router#271

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.07%. Comparing base (9650075) to head (8817b30).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #231      +/-   ##
==========================================
- Coverage   97.11%   97.07%   -0.04%     
==========================================
  Files          20       20              
  Lines         623      616       -7     
  Branches      143      139       -4     
==========================================
- Hits          605      598       -7     
  Misses         18       18              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[exoego]

Thanks.
This fixes #227

Do you think hanami/router#271 is not an issue in Hanami, but in rspec-openapi?

[AlexeyMatskevich]

I talked about a similar problem on the hanami forum (I advise you to write there by the way, because they almost never respond in github and other places) - apparently, this is not an issue, but an undocumented nuance of operation.

They have examples of their work in their documentation https://www.rubydoc.info/gems/hanami-router/Hanami%2FRouter:recognize. And there are examples of work with and without Rack::MockRequest, but there is no description of such nuances that without Rack::MockRequest recognition does not always work validly.

So I think it's just a Hanami documentation problem.

[AlexeyMatskevich]

@exoego Is there anything else I need to do in this MR?

[exoego]

Thanks.
Released in https://github.com/exoego/rspec-openapi/releases/tag/v0.18.3