@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"