generate source code from ring.util.http-response functions

[ikitommi]

Separate spray-code-extracting to user-namespace, build source code to 'ring.util.http-response` from there

• better ide-support (autocomplete & refactor)
• faster (don't have to expand macros in client projects)
• spray2clojure code will be in this codebase, can be rerun easily

[ikitommi]

idea continued:

• separate EDN-file containing the http-statuses
• access to the EDN-data at runtime
• generate also a separate namespace with http-response-codes by name:

(ns ring.util.http-response-codes)

(def ok 200)
...
(def not-found 404)

... would help in writing documentation per status code:

(require '[ring.util.http-response :as h])
(require '[ring.util.http-response-codes :as hc])
{:responses {hc/ok {:schema Pet}
            {hc/forbidden {:schema ForbiddenForest}}}

...

(def handler [request]
   ...
   (if valid? (h/ok a-pet) (h/forbidden a-forbidden-forest))

[ikitommi]

relates to #2