Fork me on GitHub
#reitit
<
2018-07-25
>
ikitommi08:07:39

@zarkone looks ok to me, I think it could be simplified a bit.

ikitommi08:07:44

wrote the “nesting routers” guide, just for the core router, but here it is: https://metosin.github.io/reitit/advanced/composing_routers.html

zarkone08:07:02

oh, new doc section looks really nice! will definitely use it, thanks!

delaguardo13:07:03

Hi! I just start using 0.1.4-SNAPSHOT and now I got routes conflict

clojure.lang.ExceptionInfo: Router contains conflicting route names:

:firebird-external-web-server.router/endpoints
-> /rocket-team/gify/random
-> /rocket-team/gify/gif/:id

delaguardo13:07:38

But those routes doesn’t seem to be in conflict at all

ikitommi13:07:53

@delaguardo that seems to be a name conflict.

ikitommi13:07:00

e.g. both routes have a same :name, making the reverse routing undeterministic. Can't be turned off.

ikitommi13:07:26

I that a good idea?

delaguardo13:07:33

yes, you are right. It was because of names. sorry for noise

j0ni18:07:50

hey @ikitommi a meta-question for you - is reitit at least as well supported as compojure-api? I'm curious about whether metosin is more enthusiastic about this project than compojure-api - we use compojure-api a lot right now, and tho I like it, I like the look of reitit more. I'm sensitive to outrageous fortune however - I accept the risks of abandonment or project leads falling out of love with projects for whatever reason (/me looks askance at the nervous systems fink-nottle repo, recently archived) but getting some intel about what metosin is feeling about reitit vs compojure-api would be helpful.

j0ni18:07:00

Cheers for all the excellent work you all do