probably yes, or just send JSON or transit

Ring by itself doesn’t work. I can do JSON, but considering ring doesn’t work, there are a bunch of other things like cookies and so on. Maybe it is time to move this to Clojure

Can you be more specific on "ring by itself doesn't work"?

E.g. what did you try and what error did you get. There might be ways to fix it

Here’s my bb.edn(simplified)

{:paths ["src"]
 :deps {ring/ring-defaults {:mvn/version "0.3.4"}}}

user=> (require '[ring.middleware.defaults])
clojure.lang.ExceptionInfo: Unable to resolve classname: java.net.JarURLConnection [at ring/util/response.clj:278:20]

https://github.com/ring-clojure/ring/blob/1db1b306ce8ec4db2f17a8cb0c9c98fe7f90146f/ring-core/src/ring/util/response.clj#L277

(ns bbform)

(require '[org.httpkit.server :as srv])
(require '[babashka.deps :as deps])

(deps/add-deps '{:deps {ring/ring {:mvn/version "1.10.0"}}})
(require '[ring.middleware.params :as params])


(defn show-params-handler [req]
  {:body (pr-str (:form-params req))})

(def handler (params/wrap-params show-params-handler))

(srv/run-server handler {:port 1234})

(println "Running server on ")
@(promise)

curl  -d foo=bar
{"foo" "bar"}%

with cookies:

(ns bbform)

(require '[org.httpkit.server :as srv])
(require '[babashka.deps :as deps])

(deps/add-deps '{:deps {ring/ring {:mvn/version "1.10.0"}}})
(require '[ring.middleware.params :as params])
(require '[ring.middleware.cookies :as cookies])

(defn show-params-handler [req]
  {:body (pr-str (:form-params req))})

(def handler (-> show-params-handler
                 params/wrap-params
                 cookies/wrap-cookies))

(srv/run-server handler {:port 1234})

(println "Running server on ")
@(promise)

As shown above, it's probably best to test individual middlewares. If a specific one doesn't work, welcome to post issues, they are likely fixable (either in bb or in ring)

^ @U8VE0UBBR

This works for now

Something new every month! Colocated bb.edn is a small change but reduces friction significantly

Note that the official syntax for process is now also (process opts+args) so the opts map goes first, it was "unified" with shell a while ago

Ah ok, I'll fix that

Note that you can get the behavior of your library as well when you do:

(alter-var-root #'process/*defaults* assoc :pre-start-fn ...)

Good to know, thanks

I just pushed 0.0.2 with the fix for process

I do miss set -x – thanks for starting this thread and library

Well this is why :pre-start-fn exists

@U04V15CAJ: I would like to encourage others to use *defaults* as well. (I made the library before I knew about *defaults*.) I suppose the only thing blocking me would be compatibility with older versions of bb. Would it be enough to bump babashka.process to use *defaults* or is upgrading to latest bb a requirement?

well. bb process is built-in to bb so either upgrade bb (but first it has to be released, the commit is still only on master) or require process with :reload . :reload will work in older versions

*defaults* has been there for a long time, but it wasn't properly exposed in SCI, but when you load bb process from source it will work with current versions

All right. It sounds like there is still some value in this library in the short term. I can add a note about using *defaults* in the README for those using the newest bb and deprecate the library later