Really enjoyed the article, @malcolmsparks 🙂

is there a way to extend the edn reader in yada?

@stijn: can you expand?

@malcolmsparks: trying to read the body of a Content-Type application/edn request that contains tagged literals that are not standard

so, would need (edn/read-string {:readers ...} ...)

I guess I should override (defmethod process-request-body "application/edn"

or would it be better to have an extension point for the reader itself? otherwise I'm duplicating the with-400-maybe and schema logic for reading the body

@stijn: can you expand?

I think you should override the defmethod in this case. It's not hard.

A great example of when this makes sense.

Possibly the existing implementation could be extended in some way, but it's more work

@malcolmsparks: I'll overwrite the process-request-body defmethod, seems simple enough yes

that works 🙂

cool

I just reduced around 50 API endpoints to just one by plugging an Om Next parser into a yada resource. winning

hey I was wondering if there is a completed in full resource map out there, I know https://juxt.pro/yada/manual/resources.html contains an example of one but throughout the examples used it appears in many different forms with resources nested in different ways and again just curious if one exists with everything that can be contained in the resource map