Skip to content
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

includeScript on routes or all pages rather than template-specific #26

Open
loppear opened this issue Dec 12, 2017 · 0 comments
Open

includeScript on routes or all pages rather than template-specific #26

loppear opened this issue Dec 12, 2017 · 0 comments

Comments

@loppear
Copy link
Contributor

loppear commented Dec 12, 2017

Rather than repeatedly specifying (template, entry_point), we want to one-line a common entry-point for all pages or all pages in a module.

There's a challenge with render not knowing when it's at a top-level page, however. So it may be that the fix here is to attach the entry point to a common layout for the project instead?

@loppear loppear changed the title includeScript on routes or all pages than template-specific includeScript on routes or all pages rather than template-specific Dec 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant