This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-24
Channels
- # aleph (1)
- # announcements (22)
- # atom-editor (11)
- # babashka (46)
- # beginners (60)
- # calva (44)
- # cider (18)
- # circleci (1)
- # cljdoc (12)
- # cljs-dev (5)
- # cljsrn (19)
- # clojars (3)
- # clojure (162)
- # clojure-dev (9)
- # clojure-europe (6)
- # clojure-italy (2)
- # clojure-losangeles (2)
- # clojure-nl (5)
- # clojure-spec (7)
- # clojure-uk (23)
- # clojureremote (1)
- # clojurescript (55)
- # community-development (14)
- # core-async (234)
- # cursive (14)
- # data-science (3)
- # datomic (32)
- # fulcro (5)
- # graalvm (20)
- # graphql (2)
- # hugsql (4)
- # jobs (11)
- # jobs-discuss (2)
- # joker (1)
- # juxt (3)
- # kaocha (1)
- # luminus (1)
- # off-topic (33)
- # pathom (3)
- # pedestal (1)
- # reagent (24)
- # remote-jobs (3)
- # shadow-cljs (38)
- # spacemacs (4)
- # specter (4)
- # speculative (54)
- # tools-deps (62)
- # vim (8)
- # vscode (14)
I’ve release 3.1.5 of Fulcro. Some minor bug fixes, including one for the websocket preload for using Electron version of Inspect. There are also new versions of the Electron binaries 2.3.0-RC2 on github that have various improvements/fixes. I still need to rework the settings for Electron so you can set the websocket server port, but if you’re ok with the default port then they should work fine. https://github.com/fulcrologic/fulcro-inspect/releases/tag/2.3.0-RC2
Q: I have a form with nullable numeric fields, using Fulcro form support. I noticed that when cancelling a form (thus reverting to the pristine state), nil values that were edited to a non-nil number, were not reset. I solved this by adding a (postwalk prim/nillify-not-found data-tree)
in the pre-merge of the loading component. Is this a reasonable approach? Any better suggestions? Thx (fulcro 2.8)