Our great sponsors
-
-
Syphon
An Elm-like language for declarative, purely functional GUI applications powered by Electron and React (by georgegarrington)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Thanks u/ThePyroEagle, I think all of these are sensible advice!! Our JS generation is pretty primitive right now, we are using mustache templates and there is very little semantic understanding of it in our Haskell code. I think first step will be doing some annotating, as you said, which means we add some extra info on them and then we can check that certain relations hold, and next step will be adding intermediary representation. Only possibly useful think I can say about templating is that we are using mustache templates right now and what is missing is a way to specify in types, for each template, what are the inputs it takes. Right now they just take any types / JSON and that is too loose. So next step will be using some better templating mechanism. I wrote a bit more about it here: https://github.com/wasp-lang/wasp/issues/124 .