Closed ilkosta closed 11 years ago
Hi @ilkosta, nice feature! I can see how that could be useful for structuring templates. For angular-brunch-seed I think that I like the way we have it now, though. If we move the jade-generated templates to a separate directory then we would have to change the templateUrl
s in app.coffee
e.g. '/partials/jade_assets/partials1.html'
. This would cause us to have different locations for html and jade users. I would like to keep these files in the same if possible. I can see how the current implementation carries with it the risk of overriding html files, though. And I do believe you have an excellent solution to that problem.
Hi, with the last version of static-jade-brunch is possible to place the compiled files in a specific
asset
directory. I think that this is useful and more clean.