Kimmo Koskinen

Whipped up a quick fix in #4. Seems to work in my project, though I have some other problems there too :D

Actually, it could also holy-lambda proper would keep the headers map with strings as keys, but not sure what that would cause downstream.

Right, for the core, a flag sounds reasonable for backward compatibility. And we can document the flag too. I was wondering then the holy-lambdaring-adapter. I guess normalizing header keys is...

> Just do it in the core. It's safer that way. Yup, I'll see when I'll get to that :) > By the way, do you see any other issues...

Yeah, doing this in the adapter would be good for users I think, I just didn't yet have change to propose :) I think `RingResponseBody` would have to take the...

One thing to be aware of could be the encoding of the InputStream/ByteArray so that the String is created in with the encoding of the bytes. We might want to...

I ran into this also, and found an [SO post](https://stackoverflow.com/a/15557636), which points to [org.apache.poi.ss.usermodel.DataFormatter.formatCellValue](https://poi.apache.org/apidocs/dev/org/apache/poi/ss/usermodel/DataFormatter.html#formatCellValue-org.apache.poi.ss.usermodel.Cell-), which seems useful, based on the javadoc, if you want a string that looks the same...

To outline this a bit more, the Clojars artifact also contains a `public/index.html` entry, in which case, any user of this library, serving a `index.html` via `(io/resource "public/index.html")` risks getting...

Neat! I guess adding `resources/public` to `:clean-targets` in project.clj or putting the dev time cljsbuild to `:dev` profile together with a separate resource path + clean-target, could avoid putting compilation...

Thanks! Did a quick try, but seems it didn't help. Thinking that the power of Leiningen `{:global-vars {*print-length* 100}}` in ~/.lein/profiles.clj seems to escape my understanding. My current workflow is...