Default (optional) param value in route definition

[thiagomajesk]

@fuelen

This can be resolved by simple plug, which redirects to /logs?days=1 if days parameter is empty

Are you talking about forward/4? I think it’s only helpful for static routes. For multiple optional parameters, I’d have to match for every possible combination (eg.: /logs?days=7&limit=10&level=error). Also, there’s this disclaimer from the docs:

However, we don’t advise forwarding to another endpoint. The reason is that plugs defined by your app and the forwarded endpoint would be invoked twice, which may lead to errors.

I was specifically looking for a different solution, something more in line with what Ruby does. I guess I’d have to spend a little more time on generic implementation to be able to reuse it with other routes.

@NobbZ

Don’t match on days , but do something like this in your action:

days = Map.get(params, "days", 1)

Please, see my previous comment on why I’m looking for a different approach than this one:

@thiagomajesk

I know we could simply do that by hand merging the conn.params values with a default map after the action was already matched, but the problem with this approach is that the route won’t change to represent the current page state