-
Notifications
You must be signed in to change notification settings - Fork 402
Update routing-controllers class-validator dependency to latest (0.9.1) #424
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
Comments
Last publish 5 months ago, it seems abandoned. |
I hope not, since it's quite the best framework to get some architecture to the nodejs mess for bigger projects. |
I have access to master branch but no access to npm to publish package. So last year when I created the PR #315, I published it as |
@19majkel94 I tried doing the same (created my own routing-controllers package on npm), and after |
@MardariG will give it a try... are you using your version as part of the TypeORM stack? |
Sorry I deleted the comment, didn't noticed 19majkel94 has published already another version; https://www.npmjs.com/package/@mardari/routing-controllers Yes, I'm using it in https://github.com/w3tecch/express-typescript-boilerplate boilerplate, as with official version validation of @Body is not working. |
@MardariG I had also done the exact same with my package, and now I have replaced with your version of Routing-Controllers and I still get the metadata error log and no validation happens.
I am using the exact same boilerplate and not having any luck with the validation. Any ideas what else I could look at? I have checked the app's node_modules, and there is only one version of class-validator in the root of the app's node_modules. I have also checked Routing-Controllers folder and there is definitely not a copy of class-validator in there. Im running out of ideas here. |
FSM1 can you share your error trace? |
@MardariG not getting any errors. I just get a console log from class-validator that no metadata has been found, and a response of an empty ValidationErrors array, even though the request is invalid.
the following is logged to console when executing:
|
FSM1 can you share your |
|
FSM1 Strange, using this https://github.com/w3tecch/express-typescript-boilerplate template, all I have to change is replacing official You can clone a clean project and see what is different from yours. |
I have changed quite a bit from the original boilerplate (ripped out TypeORM and using Mongoose + Typegoose instead). Class-validator should be quite agnostic to that though. I am using other annotations throughout the project without issue. Think I am just going to give up on the W3tecch boilerplate and move on over to Nest.js, hopefully with a lot less issues and a bit more support. thanks for the help @MardariG |
Stale issue message |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Please could you update the class-validator dependency to the latest version (0.9.1)?
If I use the latest version (0.9.1) and routing-controllers is still using the older version (0.8.5) then oddities occur as described in this issue by @NoNameProvided
typestack/class-validator#166
EDIT: should class-validator be a peer dependency?
As always, thanks for your awesome efforts guys :)
The text was updated successfully, but these errors were encountered: