Martin Klepsch
Martin Klepsch
Hey @cjhowe7 that sounds like a good suggestion - do you know if the value of cider-boot-parameters has any effect on what is being ran when you execute cider-connect? Cheers
If a `:main` option is going to be implemented into `boot-cljs` there would no modification be necessary. https://github.com/adzerk/boot-cljs/issues/11
boot-cljs has a `unified` option again: https://github.com/adzerk/boot-cljs/commit/7fd294344fa27ae1176d5eab103e4d980af21ffb which makes any html munging unnecessary. Any contributions for a simple server side component are welcome!
/cc @donmullen @pandeiro
Potentially this can be achieved in a generic way by making a `boot-ring` type of task similar to @pandeiro's `boot-http`. This way a handler could be specified and you're good...
Can you provide your `build.boot`?
I agree that datascript is nice but I'd like to keep most of the options to this template to add something to the build setup. Them Om and Reagent options...
We could also rename the task. I often use `test!` as a task name to avoid collision.
I like re-frame a lot, if it can be added without making the generation code much more complex I'm happy to. In the past I've been fine with adding re-frame...
[deleted / invalid]