On 3 Dec 2013 23:28, "James Laver" <james.la...@gmail.com> wrote: > Some examples: > 1. The :params key is used by ring.middleware.params, compojure and ring.middleware.format so it's impossible to know where a given param is coming from > 2. ring.middleware.params does not provide a convenience map that merges :query-params and :form-params, despite being happy to stuff everything into :params. At least ring.middleware.format adds :body-params here. I've now written a middleware to do this. > 3. ring.middleware.keyword-params only keywordises the :params map, not the other maps. There is no configurable behaviour to ask it to do other maps. I've now written a middleware for this
It sounds like part of the issue is with ring.middleware.format overloading the :params key, but it also seems like you might have an unusual set of requirements. The custom middleware you describe sounds like one or two lines of code. Did you find it took particularly long to write? Others have mentioned Liberator, which I'd highly recommend using for RESTful web services. It gets rid of a lot of the boilerplate required, at least the parts that deal with HTTP. - James -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
