-
First of all, thank you for building this really cool tool. I'm enjoying exploring it! I did hit an issue that may block me from using it though. Mockoon seems to be using the wrong endpoint for a request. I have the following 2 endpoints:
The issue is that when I try to call the second endpoint by using query parameters, Mockoon recognizes it as calling the first parameter with route param id = search. And therefore finds nothing. Is there a way to make Mockoon recognize that I'm calling the second endpoint due to the fact that I'm using query string? Am I doing something wrong here? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Mockoon is using Express.js, so all of Express' routing rules apply.
|
Beta Was this translation helpful? Give feedback.
Mockoon is using Express.js, so all of Express' routing rules apply.
If you define your routes in this order, the
:id
parameter will "intercept" the/MyService/Clients/search
call and considersearch
to be the id.You need to reorder your routes by drag and dropping them, to put the more specific first: