Currently, the CLI warns about missing @abp/ng.schematics package, but does not warn if the version does not match. This may be intentional, so there should be no hard error, but especially when there are breaking changes, the developer should have some clue to find the source of the problem.
An example error the developer gets currently:
››› abp generate-proxy [11:58:06]
[14:08:12 INF] ABP CLI (https://abp.io)
[14:08:13 INF] Version 3.1.0-rc.4 (Prerelease)
An unhandled exception occurred: Schematic "proxy-add" not found in collection "@abp/ng.schematics".
See "/private/var/folders/_b/w1h2sp4x05d595p1hvs2_q0h0000gn/T/ng-BOWqYH/angular-errors.log" for further details.
The project has the schematics installed, but the version is an earlier one. The proxy-add command was added after that version and ABP CLI tries to invoke it. There is no information regarding mismatching versions, so the developer would think the proxy generator is proken.
Currently, the CLI warns about missing
@abp/ng.schematicspackage, but does not warn if the version does not match. This may be intentional, so there should be no hard error, but especially when there are breaking changes, the developer should have some clue to find the source of the problem.An example error the developer gets currently:
The project has the schematics installed, but the version is an earlier one. The
proxy-addcommand was added after that version and ABP CLI tries to invoke it. There is no information regarding mismatching versions, so the developer would think the proxy generator is proken.