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
There is an trip using class-validator without defining the self's container.
The routing-controllers directly dependent the class-validator package , But my project not.
so I need add the class-validator package to my dependencies , so that I can easy add The limits(example:@Length(10, 20)) to my dto class.
But my denpendent class-validator is different with the routing-controllerss dependent class-validator.So they use their self's defaultContainer.
It make some confused problem that my limits not valid in controller actions.
The text was updated successfully, but these errors were encountered:
Maybe routing-controllers package can move the denpendency class-validate to the peerDependencies.
That users must install class-validate himself.
Maybe the default validate switch should be false.
@chianquan same here! i have to fork this repo and modify the original code to avoid that kind of errors also i have to create a scoped npm package @propellerheads/routing-controllers
There is an trip using class-validator without defining the self's container.
The routing-controllers directly dependent the
class-validator
package , But my project not.so I need add the
class-validator
package to my dependencies , so that I can easy add The limits(example:@Length(10, 20)) to my dto class.But my denpendent
class-validator
is different with therouting-controllers
s dependentclass-validator
.So they use their self's defaultContainer.It make some confused problem that my limits not valid in controller actions.
The text was updated successfully, but these errors were encountered: