Affects Version/s: PUP 3.4.3
Fix Version/s: None
A minor inconvenience when building modules.
Runningon a module with a malformed custom type results in the build failing with no error returned, even if debug and verbose flags are set it just returns a failure exitcode. Took a while to pinpoint the rogue file without any feedback from the build.
You can replicate this as follows:
Setting the malformed type to:
Building this module now fails without warning
Is there a way of validating the ruby parts of the modules, the parser returns the Ruby DSL is deprecated warning.