Closed jipiboily closed 6 years ago
@jipiboily When I built this gem, mjml
on the command line was failing silently too, so if they've introduced errors now and you can see an easy way to catch them and raise them in Rails, then please do add those changes.
It looks like a bunch of errors are still silent.
If I dig into the code again or face silent errors I might tackle this. I don't have much free time right now, though.
@jipiboily No problems, thanks for checking it out. I'll leave this issue open for the future. :-)
@jipiboily solved by https://github.com/sighmon/mjml-rails/pull/27
If you input invalid mjml, mjml-rails doesn't raise any error and just siltenly fails.
Example:
This doesn't render and returns nothing (nil or empty string, not sure, didn't check).
It would be relatively easy to catch MJMLError or something like that and raise when we get that from the external rendering through the npm module.
Thoughts?