This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-28
Channels
- # adventofcode (2)
- # announcements (4)
- # babashka (34)
- # beginners (44)
- # biff (5)
- # calva (8)
- # cider (4)
- # clj-kondo (5)
- # clj-on-windows (5)
- # clojure (57)
- # clojure-art (1)
- # clojure-denmark (2)
- # clojure-europe (40)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-seattle (1)
- # clojure-uk (2)
- # clojurescript (20)
- # cursive (6)
- # datomic (1)
- # emacs (6)
- # events (5)
- # fulcro (22)
- # helix (5)
- # hyperfiddle (5)
- # jobs (1)
- # joyride (2)
- # lsp (8)
- # malli (8)
- # off-topic (30)
- # pathom (8)
- # pedestal (1)
- # portal (5)
- # proton (1)
- # rdf (2)
- # re-frame (4)
- # releases (1)
- # remote-jobs (1)
- # reveal (8)
- # xtdb (5)
not sure this is a portal problem or if I’m doing something stupid: I’ve got a map that’s the result of a poremesa/let and when I tap> that into portal I get something like this #ref 28748 which does make sense, but there seems to be no way to send the actual value to portal or to go from the #ref to the contents? derefing doesn’t work since the type of it is just clojure.lang.PersistentArrayMap Datafy stuff works but is cumbersome to navigate into a “normal” map.
Any ideas?
This is probably a bug in the serialization, not sure what it could be though :thinking_face: What version are you running?
I recently fixed some stuff around special double values, which would cascade into other issues
Mhh, just upgraded yesterday. I'll check the exact version tomorrow and also try with a different one
I tried with “0.26.0” and got nil instead of #ref 28748
I’m not sure what I should do to tap the content though, since the type of the thing is already correct and derefing also doesn’t seem to work 😅