Miikka Koskinen

At Metosin, I'm using Aleph in one project (a SaaS application) as the HTTP server and I've written some HTTP API clients with it as well.

In case of https://upvote.pub, it seems that nowadays connecting fails during the SSL handshake. You can't connect to it with cURL or a browser, either. Probably the service has been...

Example by @mvarela – this broken schema is quietly accepted, but ideally it would give a syntax error: ```clojure ;; Broken: :version schema is accidentally included in :project vector (def...

As a workaround, you can directly depend on a newer version of `cljsjs/material-ui`. I've been using these dependencies for a while and it seems to work fine: ```clojure [cljs-react-material-ui "0.2.50"...

Yes, so there's no established convention on which case should be used by the application and the middlewares to avoid exactly this situation.

I don't know if there's a fast way. I suppose that ultimately this is a bug in the Ring spec, since it does not specify how to handle response headers...

I guess Ring's answer to this problem right now is that you should use `find-header`/`get-header`/`update-header`: https://github.com/ring-clojure/ring/blob/1d858fb13381e92f5ced4dedf42853fc062ace8c/ring-core/src/ring/util/response.clj#L186-L209

I think that we should use the default tags where possible: in EDN, `java.time.Instant` should be tagged as `#inst` and in Transit it should use one of the time tags...

It certainly is surprising behavior. For comparison: ```clojure (def spec-a (ds/spec ::spec-a {:x int?})) (def spec-b (ds/spec ::spec-b {:x nil?})) (s/valid? spec-a {:x nil}) ;; false ``` The idea is...

One explanation is that `explain*` for `st/Spec` calls both `conform*` and `explain*` on the underlying spec. ```clojure (s/def ::a #(do (prn ::a %) (int? %))) (s/def ::b (st/spec ::a)) (s/explain-data...