routing-controllers refers to a concrete version(0.10.1) of class-validator
https://github.com/typestack/routing-controllers/blob/a00d08dcf5a4fc2b03bbc45f582a2f44c23576ce/package.json#L87
instead of typical 'auto-update patches and minor versions' approach, like ^0.10.1.
For example, class-transformer is used with mentioned auto-update approach:
https://github.com/typestack/routing-controllers/blob/a00d08dcf5a4fc2b03bbc45f582a2f44c23576ce/package.json#L86
So I can't update to the latest version of class-validator (0.11.1).
Why it was done in this way?
same question here. is this something like misspelling issue?
bump @pleerock @MichalLytek
@zefexdeveloper ping @jotamorais, not us, as he's the maintainer now 馃槈
This was introduced in #472 and it has been object of several discussions previous to that (whether to keep as a project dependency or move it to peerDependencies exclusively.
For now, I will fix the auto-update, but need feedback whether it makes sense for class-transformer & class-validator to move to peerDependencies only.
Related: #369, #384 and #452
@jotamorais I think it should continue as a peerDependencies. Thank you very much.
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.