Fork me on GitHub
#reitit
<
2018-12-09
>
vale07:12:29

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

ikitommi09:12:59

@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.

vale09:12:20

makes sense

ikitommi09:12:55

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

ikitommi09:12:37

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

ikitommi10:12:50

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

vale10:12:37

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

vale10:12:45

it pulls in a bunch more packages

vale13:12:01

>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?