Toying with static analysis of HTML templates
After last episode with Templ maintainers I was really pumped to try Templ and see if it would work for me. Without spoiling too much I believe it would have been easier to start from scratch with Templ vs. trying to migrate an existing project.
This led me to try and see if I could add static analysis of my templates in my library tpl. I don't really have a PoC yet, but kind of getting close to it. If everything continue I should be able to capture errors in using of wrong field in template, like typos in field name that are caught at runtime at this moment.
Links: https://github.com/dstpierre/tpl
Also if you want to support this show, this is a 50% discount on my courses: Build SaaS apps in Go and Build a Google Analytics in Go.
This led me to try and see if I could add static analysis of my templates in my library tpl. I don't really have a PoC yet, but kind of getting close to it. If everything continue I should be able to capture errors in using of wrong field in template, like typos in field name that are caught at runtime at this moment.
Links: https://github.com/dstpierre/tpl
Also if you want to support this show, this is a 50% discount on my courses: Build SaaS apps in Go and Build a Google Analytics in Go.
Creators and Guests
Host
Dominic St-Pierre
Go system builder - entrepreneur. I've been writing software systems since 2001. I love SaaS, building since 2008.
