You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When registering the same route with different HTTP methods, it seems that the latest registered route always takes precedence, no matter what HTTP method is used.
Steps to reproduce
First I register the same route twice, but on different methods.
Description
When registering the same route with different HTTP methods, it seems that the latest registered route always takes precedence, no matter what HTTP method is used.
Steps to reproduce
First I register the same route twice, but on different methods.
Then in my test I try to make the HTTP call:
But when I do that I get the second call from the
patch
callback whereas I would expect theget
callback to be called instead.Expected behavior
The adapter should only match the route if the HTTP method is the one being called.
Additional context
The text was updated successfully, but these errors were encountered: