Code generation options
# helpa
addshore
05/15/2025, 9:58 AMI have a few hundred lines of custom yaml that defines a comms protocol
Currently for go I use https://github.com/dave/jennifer to generate structs for all parts of this protocol
What sort of options might there be for toit / do any exist yet / should I try and handroll something for now?
f
floitsch
05/15/2025, 10:00 AMGood question. It depends a bit on the protocol.
I have been working on a Toit mustache library. If your protocol is structured enough you could just generate code this way.
I don't think there is any Toit AST library otherwise. Could be interesting.
If you are interested in the mustache library ping me, and I will share what I have so far.
a
addshore
05/15/2025, 10:23 AMdefiantly interested in that library
A simple version of what I plan on generating (currently hand crafted) https://github.com/lightbug-io/toit-lightbug/blob/main/src/messages/m11-open.toit
And a more complex one https://github.com/lightbug-io/toit-lightbug/blob/main/src/messages/m15-last-position.toit
Generated from yaml that looks something like this https://github.com/lightbug-io/docs/blob/main/public/files/protocol-v3.yaml
f
floitsch
05/15/2025, 10:27 AMHere is my code: https://github.com/floitsch/toit-hue/tree/floitsch/2025-03-13/tools
floitsch
05/15/2025, 10:28 AMIt's in a branch, and not everything is finished (which is why I haven't published it yet).
The mustache library should be good, though.
floitsch
05/15/2025, 10:29 AMI might have slightly more recent code. Let me have a look and push it if necessary.
floitsch
05/15/2025, 10:32 AMSo the way I set this up is: I write Toit code "normally", with "// MUSTACHE" comments.
I then replace these strings with the corresponding mustache templates.
The result is then used as input for the mustache library.
This avoids writing Toit code in a mustache file where there is no code completion...
Here is an example: https://github.com/floitsch/toit-hue/blob/floitsch/2025-03-13/tools/openapi-template/api.toit
floitsch
05/15/2025, 10:34 AMHere is the conversion from Toit file to mustach template.
https://github.com/floitsch/toit-hue/blob/floitsch/2025-03-13/tools/openapi-gen.toit#L284
And immediately afterwards is the application.
a
addshore
05/15/2025, 10:35 AMvery nice 🙂 I expect I'll be taking a look at this in the coming days!
f
floitsch
05/15/2025, 10:36 AMI hope it works for you.
Eventually all of these will become their own packages, etc. But that will take time. (I have been working on this for more than a year now...).
floitsch
05/15/2025, 10:38 AMI usually work on this project when I travel, which is happening this weekend. I will probably start by making the mustache library its own package. That's probably the most useful now.
floitsch
05/17/2025, 9:50 AMrepository has been created and PR is uploaded: https://github.com/toitware/toit-mustache/pull/1
a
addshore
05/28/2025, 9:38 AMSo, giving it a go, but i still have never really had toit installed, only primarily use it via jag.
the makefile hardcodes @toit
What do you think is the path of least resistance for me? 😛
I always thought it might be neat to have a
jag toitaddshore
05/28/2025, 9:38 AMI always forget where it installs it
addshore
05/28/2025, 9:39 AMbut maybe i should just install toit 😛
addshore
05/28/2025, 10:13 AMInfact, I might just generally need some more guidance on that repo and how to build the tool.
I managed to get make to work for me with a makefile alteration https://github.com/addshore/toit-mustache/commit/0f07d8818ecfc4c668e8bbe0c2e6d3d5d9f5fc02
however
./build/mustache./build/mustache --helpf
floitsch
05/28/2025, 10:30 AMjag toitfloitsch
05/28/2025, 10:32 AMbuild/mustache -hfloitsch
05/28/2025, 10:33 AMargh.
floitsch
05/28/2025, 10:33 AMmy mistake.
floitsch
05/28/2025, 10:33 AMfixing it.
floitsch
05/28/2025, 10:35 AMFix is uploaded.
a
addshore
05/28/2025, 10:57 AMAmazing, I might try and take another look at it today 😛
2 Views