-
Notifications
You must be signed in to change notification settings - Fork 326
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
Introduced Groovy MarkupTemplateEngine #185
Introduced Groovy MarkupTemplateEngine #185
Conversation
The Template Engine is registered for template files with suffix '.tpl' It is basically a clone of GroovyTemplateEngine using the Groovy MarkupTemplateEngine. Because there are refactoring pull-requests out there, I skipped refactoring those two Engines for now.
1 similar comment
thanks @melix for the clue. I didn't dive that deep but I'll reconsider it. |
createTemplateByPath is the preferred method to parse templates. see http://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html#_creation_of_a_template_engine
Thanks so much, I've wanted to add support for this for a while now! |
👍 |
You're welcome ;) |
Hi. It's been a while, but I finally finished an example project using Groovy Markup Templates. To test the distribution I added a feature branch too. |
Thanks again Frank, I've got some spare time again now so I'll make sure to review this as soon as possible and then work out when we can get it into a release. |
👍 |
+1 |
The Template Engine is registered for template files with suffix '.tpl'
It is basically a clone of GroovyTemplateEngine using the Groovy MarkupTemplateEngine.
Because there are refactoring pull-requests out there, I skipped refactoring those two Engines for now.
To unify the Renderer Tests for different TemplateEngines there is a new Spock-Test called RendererSpec.