Default segment specification in named routes

[GetContented]

I'd like to be able to specify a route similar to this:

(defroute my-path "/design/:filter-name/:id" [filter-name id]
  ; do something
  )

(my-path {:id 5}) ; currently yields "/design/:filter-name/5", but I'd like to be able to specify a default for filter-name

And have the generated named path be able to specify default values to the parameters, rather than a keyword being used. I'm not really sure how this could be accomplished.

This is pretty closely related to having trailing slashes being elided, too... these two use-cases seem to be common enough that a solution would be really great to have in secretary itself, perhaps.

[GetContented]

Nevermind. I worked out how to do this with standard defn calls and by using more defroute calls.

[gf3]

Yay!

[GetContented]

Could probably deal with some tasty macros sometime tho to make this common stuff easier, IMHO... after I've used it for a bit longer if I have something extractible, I'll submit a PR :)

[gf3]

@JulianLeviston you might actually be able to accomplish what you suggested with "nested routes" which are upcoming in 2.0.0.

[GetContented]

Yep, that sounds about right :). Hopefully they treat unspecified intervening route segments in a nice way (ie with supplied defaults).

[noprompt]

@JulianLeviston I would hold off until the 2.0.0 stuff is ironed out. IMHO I don't think adding more macros to the library will buy is anything a programmer couldn't do themselves. At the company I work at, we've been developing against using the 2.0.0 branch and have been able to do everything without macros - including context. Have a look at #50.

[GetContented]

Cool. Still think it'd be nice and useful to have defaults for segments. All good tho :) 2 looks awesome!

[noprompt]

@JulianLeviston I misread your original request. I think defaults might be possible. Let me think about.