This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-28
Channels
- # announcements (1)
- # aws (1)
- # babashka (41)
- # beginners (21)
- # biff (7)
- # calva (102)
- # cider (8)
- # cljs-dev (1)
- # clojure (8)
- # clojure-bay-area (2)
- # clojure-dev (30)
- # clojure-europe (40)
- # clojure-norway (52)
- # clojure-sweden (9)
- # clojure-uk (5)
- # clojurescript (15)
- # cursive (7)
- # data-science (1)
- # datomic (23)
- # events (1)
- # fulcro (9)
- # humbleui (23)
- # hyperfiddle (46)
- # introduce-yourself (1)
- # jackdaw (2)
- # jobs (2)
- # london-clojurians (1)
- # malli (13)
- # off-topic (8)
- # re-frame (36)
- # remote-jobs (1)
- # shadow-cljs (4)
- # specter (4)
- # squint (1)
- # transit (4)
- # vim (1)
Hi all. I have used specific transit handlers for specific types/classes of object previously - is there a way of taking special care of long values in a map - either by virtue of me adding metadata to that specific value, or by virtue of the key used in that map? Do I override handling of all maps and add processing of the keys, or is there a better approach? I have an issue with clojurescript not handling very large long values that would be awkward to fix at my API level, but fixing via transit might work. All advice gratefully received!
Instances of clojure.lang.BigInt (i.e. number literals followed by N, as in 7N) are serialized with their own tag.
If you can live comfortably with BigInts, you can simply switch to those.
Alternatively, it might be possible to override the default long reader on the CLJS side so that it returns instances of js/BigInt.
> issue with clojurescript not handling very large long values To be clear, that's not CLJS, that's JS. CLJS cannot possibly have a way around that, apart from implementing a complete number stack on its own and changing every single aspect of the internal machinery and interop.
That’s a great idea thank you. If I preprocess the data to be outputted to coerce the values to BigInt then I can leverage that, and not have to change other server side machinery to deal with strings.