Jade partials not picked up if underneath a sub-folder

[geeklisted]

Kyle - I don't know enough to say whether this is an Angular-Brunch-Seed issue, or something more inherit to Brunch.io itself.

However, I attempted to include a partial Jade template that existed in a sub-folder to /partials.

Node reported that the app compiled, but I noted that the web page would basically auto-reload over and over --- meanwhile, it would never display the underlying included content.

I 'fixed' the issue by moving my Jade template from the sub-folder to the main /partials folder and redirected my ng-include to the new location, and it worked fine.

I'm an organization nut when it comes to my web app projects; can you tell me if this is inherit to Brunch or this particular seed?

Thanks.

[kylefinley]

I believe this is a bug / feature of jade-angularjs-brunch -- relevant code. It looks like it flattens the path. So: app/partials/subdirectory/example.jade becomes: /partials/example.html

I can see how this might causing naming conflicts, however. Would you mind filing a bug with jade-angularjs-brunch/issues? @GulinSS will be in a better position to explain the reasoning behind this decision.

P.S. If you are not sure what the path maybe you can check it in the _public/js/partials.js file.

[sanfordredlich]

I think this should be solved in the latest code. In #88, the partials are in sub-folders and are picked up, no problem. - S.