so i have routes on the format:

(POST "/route" []
        :coercion :schema
        :responses {200 {:schema CompleteSchema}
                    400 {:schema {:error String}}}
        :body [use-case CompleteSchemaWithoutId]

but when posting to the route it still tries to put stuff in the database

even though it doesnt match the schema

(compojure-api / 1.1.0)

@jooivind the named :coercion is introduced in 2.0.0, the 1.1.0 uses the old (hairy) way. Can’t remember the old syntax anymore. Sadly, the wiki-pages are out-of-sync (mostly ported to 2.0.0 already) 😞

but removing the :coercion it works.

1.1.0 uses only Schema.

yeah it was kinda hard to browse the 1.1.0 documentation

would you recommend just upgrading to 2.0.0?

there are no branches in the wiki 😞

cause i kinda want to get coercion up and running as well

for non-prod, definetely 2.0.0. For prod, at your own risk. Mostly stable, but still alpha.

(we have had alpha running in prod for long time already)

thanks 🙂

Ah, the old Google way. Keep a beta/alpha badge on everything perpetually even though it’s production quality. 🙂

Seems fairly common in Clojureland

@henrik that 😉 the first alphas with Muuntaja had lot of small issues with backwards compatibility, now as stabile as it gets (also used by Luminus & Duct), the spec-coercion might still have issues. Feedback welcome.

Cheers @ikitommi, I will 🙂

fwiw, I've had various 1.2.0 snapshots and 2.0 running prod for my site's backend (http://curiosity.com) since early this year

obviously need to test releases and when stuff breaks you have to jump in, but it's been stable enough and the perf has been worth it