in the ring-http-response helper lib, could you explain why it's necessary to import all that stuff from ring.util.response?

@vale legacy reasons, it was initially made as a drop-in-place replacement for ring.util.response, which has all those things. Today, I think it’s a bad idea.

makes sense

how would you do that? just the http-response functions in a ns?

also, the ns name is too long, maybe that should be cleaned up and put into something like reitit.ring.response?

not sure if hoarding things into submodules is a good idea in a long run.

mostly i'd just want to get rid of the ring-core dependency

it pulls in a bunch more packages

>just the http-response functions in a ns yeah like that. that's all i use from it -- not sure if people need the ! versions?