This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-25
Channels
- # 100-days-of-code (3)
- # beginners (80)
- # cider (53)
- # cljdoc (9)
- # cljs-dev (66)
- # cljsrn (6)
- # clojure (108)
- # clojure-austin (5)
- # clojure-dusseldorf (1)
- # clojure-italy (9)
- # clojure-losangeles (2)
- # clojure-nl (4)
- # clojure-spec (40)
- # clojure-uk (46)
- # clojurescript (60)
- # cursive (119)
- # datomic (28)
- # emacs (10)
- # events (1)
- # figwheel-main (21)
- # fulcro (16)
- # hyperfiddle (10)
- # immutant (2)
- # leiningen (1)
- # liberator (5)
- # nyc (1)
- # off-topic (36)
- # onyx (4)
- # pedestal (52)
- # portkey (5)
- # re-frame (11)
- # reagent (11)
- # shadow-cljs (46)
- # sql (1)
- # unrepl (2)
Hi friends, I see that the portkey/aws-clj-sdk depends on aws-sdk-ruby in its api-resources directory. I’m assuming this is to get access to the machine readable json specifications that the ruby version has. Does anyone know off the top of their head where THAT library gets those json specifications from or should I just keep digging?
I believe it comes from an internal repo at Amazon. It would be cool to find a public source.
Agreed. I’ll keep digging. I just found https://github.com/clojure/java.data and my mind exploded with the (percieved) simplicity this brings (has been bringing!?) to the clojure/java interop story. I’m excited to find those json specifications though to create specs like we have here in portkey.