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
I am using typescript generator as part of my build process using a maven plugin.
When a class cannot be found (e.g. because of a typo in the type name in pom.xml) then an error is printed, but the build continues. However this will naturally result in an incomplete output file which will cause some confusion when that incomplete file is used elsewhere.
It would make it easier to detect such an error early on by failing the build process and thus alerting the user.
The ClassNotFoundException is currently caught, printed and then ignored here:
@yankee42 you are right, this is not optimal.
This behavior (continuing after error) was added as part of solving class loading problem (#142). I will consider to changing it, maybe it is not needed anymore.
I am using typescript generator as part of my build process using a maven plugin.
When a class cannot be found (e.g. because of a typo in the type name in pom.xml) then an error is printed, but the build continues. However this will naturally result in an incomplete output file which will cause some confusion when that incomplete file is used elsewhere.
It would make it easier to detect such an error early on by failing the build process and thus alerting the user.
The
ClassNotFoundException
is currently caught, printed and then ignored here:typescript-generator/typescript-generator-core/src/main/java/cz/habarta/typescript/generator/Input.java
Line 176 in 63ee545
The text was updated successfully, but these errors were encountered: