-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify template root path #192
Comments
+1 for the configurable option. |
Thoughts from the authors? Would you accept a pull request adding the configurable option? |
Sounds good to me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using Jammit, we run into a slightly sticky issue as an app grows from one template subdirectory to multiple template subdirectories.
Let's say you place templates in
app/templates
. You work for a while on the "Tasks" feature, placing templates underapp/templates/tasks
. So, window.JST looks something like:Now, you add another directory under
app/templates
, sayapp/templates/user
. Now, all JST references are prefixed with their parent directory name so they are unambiguous:This breaks existing JST references. We've worked around this in new apps by monkeypatching the jammit base template path to a fixed parent directory from the get-go:
What do you think of either allowing a configurable option? Say, an
assets.yml
entrytemplate_base_path
which, if present, is always used as the template base path. In the absence of this option, the current logic would be preserved.The text was updated successfully, but these errors were encountered: