-
Notifications
You must be signed in to change notification settings - Fork 54
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
Migration guide for Rocker users #205
Comments
casid
added a commit
that referenced
this issue
Mar 24, 2023
Thanks for sharing @nedtwigg! I added a migration section to the jte documentation and included a link to this issue. And nice one, ship-of-theseus upgrade is the way to go. Good luck with the migration! |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have used fizzed Rocker templates for several years, and they are fantastic. My primary complaint was IDE support, secondary complaint was that the github repo didn't have public CI and it was hard to get PR's merged.
I tinkered with jte, and the IDE support is really incredible. Converting a template from rocker to jte is extremely easy, the syntax is nearly identical. I bet you could whip up an autoconverter out of just a few regexes, and we might do that at some point.
The big thing missing from jte at the moment is calling templates in a typesafe way
We filled this gap by defining
and then we wrote a little Gradle plugin that lives in our
buildSrc
directory which autogenerates Kotlin model files out of the.jte
templates which look like this:And now we are able to swap over from Rocker to JTE with very little effort. Our webapp is a monolith which has run continuously since 2011 without ever having a full rewrite, just ship-of-theseus upgrages over a decade+. So it's quite idiosyncratic, but I put our integration code up as GitHub gists in case they are helpful to others.
buildSrc
The text was updated successfully, but these errors were encountered: