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

standardize behaviour of template collisions #227

mengwong opened this Issue Oct 7, 2016 · 1 comment


None yet
2 participants
Copy link

mengwong commented Oct 7, 2016

if we define two templates with the same name, at the top-level fillTemplates, the first one gets used. not the second. (edited)

but, at the include() level, the last one gets used.

we should probably standardize this to be "use the first one" and then have people define their own Available Templates above the INCLUDE that points to the Demo Master's main Available Templates.

@wtf wtf self-assigned this Oct 12, 2016


This comment has been minimized.

Copy link

wtf commented Mar 30, 2017

It makes more sense to standardize this to use the last template everywhere. True to imperative-style side effects. B-)

wtf added a commit to wtf/legalese-google-app that referenced this issue Mar 30, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.