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
Routing-controllers uses @Body(), but this library uses @MessageBody(), so enabling validation during the bootstrap initialization would inject this function into the @MessageBody() decorator.
For current user checker
See https://github.com/typestack/routing-controllers#currentuser-decorator
Many people attach a session on the request object, so we could implement our own current user check that would have access to the io/socket instance, and access request.session.user from that request instead of using @SocketRequest() to access user
EDIT: It seems there's already a PR open with support for CurrentUser checker, what's the status on this? #23
The text was updated successfully, but these errors were encountered:
For class validation
See https://github.com/typestack/routing-controllers#auto-validating-action-params
Routing-controllers uses @Body(), but this library uses @MessageBody(), so enabling validation during the bootstrap initialization would inject this function into the @MessageBody() decorator.
For current user checker
See https://github.com/typestack/routing-controllers#currentuser-decorator
Many people attach a session on the request object, so we could implement our own current user check that would have access to the io/socket instance, and access request.session.user from that request instead of using @SocketRequest() to access user
EDIT: It seems there's already a PR open with support for CurrentUser checker, what's the status on this? #23
The text was updated successfully, but these errors were encountered: