This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-26
Channels
- # aws (7)
- # beginners (109)
- # boot (5)
- # carry (2)
- # cider (25)
- # clara (6)
- # cljs-dev (86)
- # cljs-experience (19)
- # cljsrn (1)
- # clojure (183)
- # clojure-dev (7)
- # clojure-dusseldorf (7)
- # clojure-gamedev (2)
- # clojure-greece (32)
- # clojure-italy (2)
- # clojure-norway (1)
- # clojure-russia (228)
- # clojure-sg (3)
- # clojure-spec (38)
- # clojure-uk (104)
- # clojurebridge (1)
- # clojurescript (29)
- # community-development (9)
- # core-async (118)
- # core-matrix (20)
- # cursive (5)
- # datomic (140)
- # emacs (25)
- # figwheel (1)
- # hoplon (21)
- # jobs (4)
- # lein-figwheel (2)
- # luminus (10)
- # lumo (35)
- # off-topic (137)
- # om (31)
- # onyx (62)
- # pedestal (6)
- # reagent (25)
- # remote-jobs (1)
- # ring-swagger (11)
- # spacemacs (2)
- # test-check (17)
- # uncomplicate (10)
- # unrepl (1)
- # untangled (20)
- # vim (4)
- # yada (3)
Hey, I'd like to check the version of codegen used by ring-swagger/compojure-api, but I don't see a dependency. Any ideas on where to look?
@daveliepmann there is no dependency, Isn't the codegen is just for the client generation? ring-swagger output can be validated against the swagger json schema, so I hope the client-gen just works. Are the problems with it?
@ikitommi No problem, I just need to verify the version because of a security vulnerability in an old version.
Perhaps I misunderstand the stack around it
oh, the codegen also has the server stub generation. That would be nice, to have a swagger spec and generate sample server out of it.
Hmm... actually, soon that the validation lib can changed, one could use plain JSON Schema as the validation engine. Stub generation would be trivial.
OK I definitely misunderstood the role codegen played. My mistake
Late Friday afternoon 🙂
Thanks as always for your quick help. Have a good weekend!