This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-29
Channels
- # babashka (30)
- # beginners (207)
- # biff (3)
- # calva (10)
- # cljs-dev (3)
- # clojure (34)
- # clojure-austin (3)
- # clojure-bay-area (1)
- # clojure-dev (3)
- # clojure-europe (31)
- # clojure-nl (1)
- # clojure-norway (37)
- # clojure-uk (8)
- # community-development (3)
- # core-async (4)
- # data-science (1)
- # dev-tooling (2)
- # emacs (4)
- # etaoin (12)
- # fulcro (7)
- # gratitude (1)
- # hyperfiddle (7)
- # jobs-discuss (191)
- # lsp (15)
- # malli (1)
- # other-languages (11)
- # overtone (1)
- # pathom (3)
- # pedestal (1)
- # polylith (21)
- # releases (1)
- # squint (5)
- # yamlscript (5)
Summarising the thread for my issue: it has been resolved. I now can return a string or a keyword from the dispatch function correctly. Problem wasn't the syntax of the dispatch function but the schema I had written. I used multi at the top of [::m/default [:multi ...
which causes it to get all the remaining fields as a one big clump making correct return very difficult. In my case using [::m/default [:map-of :keyword [:map-of :keyword [:multi {:dispatch custom-db} ...
syntax cleaned up the calls to dispatch from "one call that has all fields" to "multiple calls, once for each unresolved submap." and enabled the string/keyword return to work as intended.
I should've paid more attention to my schema over worrying about the nitpickings of how dispatch functions. Sorry for the bother.