This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-27
Channels
- # aws (8)
- # beginners (172)
- # boot-dev (4)
- # cider (16)
- # cljs-dev (123)
- # cljsjs (4)
- # clojure (90)
- # clojure-brasil (3)
- # clojure-dev (7)
- # clojure-dusseldorf (1)
- # clojure-finland (1)
- # clojure-italy (59)
- # clojure-russia (3)
- # clojure-seattle (2)
- # clojure-seattle-old (1)
- # clojure-spec (40)
- # clojure-uk (28)
- # clojurescript (327)
- # clojurewerkz (3)
- # code-reviews (8)
- # cursive (4)
- # datomic (24)
- # editors (1)
- # emacs (19)
- # fulcro (147)
- # funcool (1)
- # graphql (1)
- # hoplon (34)
- # jobs-rus (1)
- # lein-figwheel (5)
- # leiningen (20)
- # luminus (14)
- # midje (1)
- # off-topic (8)
- # onyx (7)
- # parinfer (47)
- # pedestal (1)
- # perun (1)
- # portkey (46)
- # re-frame (25)
- # reagent (9)
- # remote-jobs (4)
- # ring-swagger (5)
- # rum (1)
- # shadow-cljs (113)
- # slack-help (8)
- # spacemacs (7)
- # sql (9)
- # tools-deps (23)
- # uncomplicate (3)
- # unrepl (3)
- # yada (6)
Is it possible to have swagger and Lucinia at the same time?
I faced a similar challenge some weeks back, did a sample project showing that. Would raise a pr soon so +swagger and +graphql doesn't conflict https://github.com/Okwori/graphqltest
Perfect, thanks!
I guess the only thing you lose is the built in query UI that pedestal provides
You mean graph-i-ql
? That comes with it and works fine using the default post
context entry point
Really? Ok, I’ll try it.
I thought you needed to run pedestal for that.
@jmckitrick use different endpoints, ie /api/* for swagger and /graphql for lucinia
I’m reading the code generated with compojure-api, and I’m trying to understand why the home routes are wrapped in muuntaja restful-formats but I don’t see where the service routes (api endpoints) are.
compojure-api handles coercion internally, so it doesn't need to be wrapped with restful-format middleware
Thought so, thanks!