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

Options for engines #7

Closed
webuniverseio opened this issue Feb 28, 2014 · 0 comments
Closed

Options for engines #7

webuniverseio opened this issue Feb 28, 2014 · 0 comments

Comments

@webuniverseio
Copy link

Hello, I ran into situation when ect was throwing an error because it couldn't locate parent template ex:<% extend 'layout.html' %>. I was simply trying to read layout.html an of course failing. That happens because there is no way right now to pass options to engines. So... I found two ways of fixing the issue - 1) fix it on ECT side and check if root path wasn't set figure out prefix path for the first template which was passed into render function, get beginning path and assign it to the root. 2) Add engine settings parameter to render in co-views, co-render engine call and ect within consolidate (with proper fallback for backwards compatibility).
First approach would require less changes, but doesn't fix the root of the issue. Second approach opens possibility to adjust other engines as well.

I already have fixes and can create requests. Please let me know what you think.

I'll also reference that issue at ect repository to see what creator thinks about it.

Thank you

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

Successfully merging a pull request may close this issue.

1 participant