Controller function does only work if it's above other functions.
I have made a YouTube video on the behavior: https://youtu.be/1vLSRNCOXJY
#Strangest Nest.js bug with Controller function
true basin
teal oxide
Controller function does only work if it's above other functions.
I have made a...
because on line 27. you have @Get(':id'), the server will treat the toppers as a route param
green creek
because on line 27. you have `@Get(':id')`, the server will treat the `toppers` ...
^ order matters.
true basin
^ order matters.
oh i see
true basin
because on line 27. you have `@Get(':id')`, the server will treat the `toppers` ...
oh i see, thanks!!!
true basin
because on line 27. you have `@Get(':id')`, the server will treat the `toppers` ...
toppers as a route param? could you explain more? is there docs where I can read more about this behavior?
oh yeah I got it! ryt! thanksss!
teal oxide
true basin
is it best practice to give the route parameters to the bottom?
teal oxide
is it best practice to give the route parameters to the bottom?
this isn't about best practices. if you define your custom route that shares the same HTTP method below a route with a route parameter, the request won't reach it at all, as shown in your video
put some console logs in there, play around with it, pretty sure you'll get the point!