Support form-encoding namespaced keywords about ring-codec HOT 4 CLOSED

I thought about adding a option map to form-encode or to mock/request to allow different key encoding schemes, but I don't think you'd save much code, a couple of lines at most. I think it's better to perform the transformation independently of the encoding function.

from ring-codec.

What about writing a function that transforms the keys into strings:

(defn kw->str [kw]
  (str (namespace kw) "/" (name kw)))

(defn keys->strings [m]
  (into (empty m) (map (juxt kw->str str)) m))

(defn mock-request [method uri params]
  (ring.mock.request/request method uri (keys->strings params)))

from ring-codec.

Yep that's pretty much what we came up with (with some slight tweaks for unqualified keys). I could figure out what went wrong pretty quickly, but I wondered if this was something you wanted to look at fixing more generally. No problem if not, it's a pretty minor issue, easily worked around.

from ring-codec.

Cool, will close this for now then.

from ring-codec.