-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[inversify-express-utils] Nesting controllers and maintaining route context #371
Comments
Hello @PodaruDragos @Cyberuben thank you ! |
hello @andreidiaconescu.
I'll reopen this just so it's clear that it's not solved. |
I'm just getting into InversifyJS and I'm struggling to get my head around the concept of Express controllers.
Usually I write my code in such a fashion that the routing chain is executed step by step and the context of the request is incrementally stored inside the request object.
routes/index.ts
routes/users/index.ts
routes/users/posts.ts
This way I don't have to validate the user in the controller that manages the posts. How would this be achieved in a sane way using InversifyJS?
Another issue I couldn't find the answer to is the order routes are executed, such
/users/me
being executed before/users/:userId
is evaluated.The text was updated successfully, but these errors were encountered: