This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-26
Channels
- # admin-announcements (2)
- # aws (1)
- # beginners (21)
- # boot (61)
- # cider (5)
- # cljs-dev (94)
- # cljsrn (35)
- # clojure (106)
- # clojure-austin (3)
- # clojure-belgium (1)
- # clojure-dev (4)
- # clojure-dusseldorf (9)
- # clojure-greece (2)
- # clojure-mexico (1)
- # clojure-russia (40)
- # clojure-spec (61)
- # clojure-uk (17)
- # clojurescript (151)
- # code-art (1)
- # component (7)
- # core-async (4)
- # cursive (1)
- # datomic (9)
- # dirac (55)
- # funcool (12)
- # hoplon (118)
- # incanter (12)
- # jobs (8)
- # juxt (1)
- # lein-figwheel (6)
- # mount (2)
- # off-topic (2)
- # om (76)
- # onyx (28)
- # other-lisps (1)
- # planck (7)
- # re-frame (9)
- # reagent (13)
- # ring-swagger (2)
- # specter (1)
- # yada (22)
@mark.melling: I'll investigate upload to see why it isn't working
That example is quite old and experimental but even so, it should work
@malcolmsparks: Thanks Malcolm
@malcolmsparks: i did a PR which stops some errors during yada swagger generation completely blowing up the process... https://github.com/juxt/yada/pull/96
Just merged
@mccraigmccraig: merged that second one - was much nicer!
yeah, i know - sometimes i'm just too pragmatic 😬
@malcolmsparks: can you think of any straightforward way i can set CORS headers on my swagger.json ?
Did you read the docs? I believe it's done but I did run in to some issues recently on http://yada.juxt.pro.
If you can expand I can help more
i had a look at the code... couldn't see how to pass anything to swaggered
which was where i presumed it needed to go... np, i served the swagger-ui html from resources for the moment
Is a resource representation generated a "request time" usually? I don't see how I can coordinate a :properties
change with a :response
change
it looks they can be two promises
but when are the two executed?
because for :exists?
to be true it needs to happen before I return from the :response
function
or should I wrap the whole resource declaration in a function that goes to db maybe?
and return the whole thing?
but I cannot do it because I need the request context from somewhere
ah ok :response
has a :properties
subkey...let me try that
no, not really working
it looks like the :properties
in the :response
don't ovverride the ones in the resource "declaration"