Skip to content

Create a route for GET /procedures/search

Otherwise this would match with /procedures/:id and try to render the show action. Which, without an id, raises a RecordNotFound error.

It is possible to receive GET /procedures/search in case a user first performs a POST to search and later refreshes the page for example.

I had to adpt the test because of how shoulda matchers work when there are two routes leading to the same action: https://github.com/thoughtbot/shoulda-matchers/issues/225#issuecomment-17621707.

Part of #53 (closed)

Merge request reports