sprockets require_tree uses paths that are strictly relative to the file, which creates inconsistent behavior, i.e. for a directory structure like this:
// This works:
//= require app/app.js
// This should work but doesn't:
//= require_tree app/controllers
// So we have to write the require_tree as such:
//= require_tree ../../app/controllers
This might require either a patch to sprockets or a new directive processor, I'm not sure if the sprockets team would be open
sprockets require_tree uses paths that are strictly relative to the file, which creates inconsistent behavior, i.e. for a directory structure like this:
This might require either a patch to sprockets or a new directive processor, I'm not sure if the sprockets team would be open