This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-23
Channels
- # announcements (3)
- # asami (5)
- # babashka (1)
- # beginners (38)
- # biff (4)
- # calva (12)
- # cider (2)
- # clj-commons (6)
- # clj-kondo (46)
- # clj-on-windows (1)
- # clojure (50)
- # clojure-europe (41)
- # clojure-nl (3)
- # clojure-norway (2)
- # clojure-uk (16)
- # clojured (3)
- # clojurescript (49)
- # conjure (1)
- # cursive (29)
- # datahike (6)
- # datascript (4)
- # emacs (70)
- # funcool (1)
- # google-cloud (12)
- # graalvm (10)
- # graalvm-mobile (7)
- # gratitude (4)
- # hyperfiddle (1)
- # joyride (26)
- # lsp (16)
- # malli (23)
- # nbb (5)
- # off-topic (23)
- # polylith (32)
- # re-frame (23)
- # releases (3)
- # remote-jobs (1)
- # reveal (3)
- # tools-build (16)
- # xtdb (50)
I'm learning a lot from using biff with htmx, one thing I'm wondering is will there be effort to bubble up the right errors during development. I'm finding I have to switch from the console to the editor to the browser, refreshing to see if it took, etc. Is there any strategy you propose to see errors early and often and easily with this kind of workflow as it is different than my ususal react figwheel/shadow-cljs workflow
Nothing in the works yet--for myself I've just been doing the save file -> check terminal -> refresh browser window workflow--however I think it wouldn't be terribly difficult to do auto-refresh and heads-up display with htmx. We'd need to establish a websocket connection, similar to what's done in the app.clj file; modify com.biffweb/eval-files! to return the stacktrace if there's an error when reloading code; then modify com.example/on-save so that after reloading code it either sends the stacktrace (on failure) or sends a command to refresh the page (on success)
just made an issue for this: https://github.com/jacobobryant/biff/issues/117
That looks great, like how it's shaping up.