This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-10
Channels
- # announcements (2)
- # asami (2)
- # babashka (29)
- # beginners (115)
- # cider (5)
- # clara (9)
- # cljdoc (14)
- # cljs-dev (1)
- # cljsrn (18)
- # clojars (3)
- # clojure (73)
- # clojure-australia (7)
- # clojure-europe (74)
- # clojure-nl (3)
- # clojure-norway (8)
- # clojure-spec (3)
- # clojure-uk (36)
- # clojured (1)
- # clojurescript (15)
- # conjure (18)
- # datomic (6)
- # deps-new (11)
- # depstar (7)
- # fulcro (2)
- # instaparse (1)
- # jobs (9)
- # nrepl (8)
- # off-topic (21)
- # pathom (5)
- # polylith (42)
- # proletarian (1)
- # rdf (10)
- # re-frame (2)
- # react (1)
- # reagent (20)
- # releases (3)
- # remote-jobs (4)
- # rum (9)
- # shadow-cljs (79)
- # sql (11)
- # tools-deps (64)
- # vim (3)
- # xtdb (26)
hi, i have a big collection of specced data that went into mongodb and lost all the namespace info. I suppose I can transform it all by recursively using the information in (s/describe) of the top-level (big) data structure. But before doing that, I thought I'd ask if something like that already exists. Anything similar? Just to complicate it a little: there are also plenty of non-namespaced and non-specced keys that got in there as well. They shouldnt be given a namespace.
Mongodb is storing data as json. So you probably need to have some sort of convention how to encode qualified keywords to/from json
Thanks for you reply! Yeah, i realize that now, but the problem is that a lot of production data was stored without the namespace info before I noticed, and it's not something i can re-do. Anyway, the approach with using s/describe also doesnt work, because of things like merge etc. So guess I'll have to write custom code for the exact data structure.