I'd like to see post-processing support beyond the existing format options:
Template files must be named {name}.scala.{ext} where ext can be html, js, xml, or txt.
For example, a .scala.jade file would compile from twirl into scala, then the embedded text would convert from jade into html (which I imagine would show errors in context of jade code for easier debugging) or: jade processes into html, then from there into scala (which is probably more efficient). These are my assumptions without knowing too much of twirl's underlying architecture.
I'd like to see post-processing support beyond the existing format options:
For example, a .scala.jade file would compile from twirl into scala, then the embedded text would convert from jade into html (which I imagine would show errors in context of jade code for easier debugging) or: jade processes into html, then from there into scala (which is probably more efficient). These are my assumptions without knowing too much of twirl's underlying architecture.
Is this a feature worth pursuing?