Juho Teperi
Juho Teperi
Is there some reason to implement this in boot-reload? Should be quite easy to do in the app. ``` clj (defonce ctx (atom nil)) (defn init! [] (if-let [x @ctx]...
Would probably be possible for Figwheel to display any messages. Anyway as we continue to have our server, we can send errors from any boot task.
Figwheel client doesn't currently support reloading the HTML file, should be easy to implement though.
Boot-cljs already exposes the dependency order as metadata on files on fileset. https://github.com/adzerk-oss/boot-reload/blob/master/src/adzerk/boot_reload.clj#L22 Though I'm not sure how good idea using this is. I'm planning on eventually replacing the logic...
> Would be nice not to load boot-cljs with more concerns. Yeah, that's my concern also. Instead of using analysis cache files, one possibility would be to just read the...
If it's enough to access Cljs options (input directory etc.) inside cljs-test handler, the selected options could be included as metadata on fileset object (on the object itself, not per...
I have now one test in Saapas and I'll grow it after we get other issues sorted out.
In Boot the failure exit code can be set with throwing exception. Process can't be directly closed, as this would break composition with other tasks. Previously Boot-cljs-test couldn't (or didn't...
My opinion is still that proper solution will be to only just Figwheel client code, and use our own "server" (Boot tasks) which happen to provide compatible Websocket server. Based...
https://github.com/boot-clj/boot-figreload