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
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:
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.
NoNameProvided
changed the title
Reference to 0.10.1 version of class-validator
question: reference to 0.10.1 version of class-validator
Aug 9, 2020
NoNameProvided
changed the title
question: reference to 0.10.1 version of class-validator
question: class-validator version 0.10.1 explicitly required
Aug 9, 2020
typestack
locked as resolved and limited conversation to collaborators
Aug 9, 2020
routing-controllers refers to a concrete version(0.10.1) of class-validator
routing-controllers/package.json
Line 87 in a00d08d
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:
routing-controllers/package.json
Line 86 in a00d08d
So I can't update to the latest version of class-validator (0.11.1).
Why it was done in this way?
The text was updated successfully, but these errors were encountered: