Am I correct in assuming that the resource is “stats” and that country and range is just a filter over those resources? If so then use a query parameter. Something like /stats?country=us&range=1-5

Edit: This has the benefit of allowing the user to select a range in a specific country instead of one or the other

What’s the usecase for wanting URLs like this? Is there a big difference between ByCountry and General? Otherwise, filters like these are exactly what query parameters are for.

I’d still use query params for this. Instead of range I’d use from. Then you can have ranges displayed like so:

• Range of days: /stats?from=2024-20-06&to=2024-30-06
• A specific day: /stats?from=2024-30-06&to=2024-30-06
• Special case values: /stats?from=yesterday

And of course every filter you dream up in the future just works /stats?from=today&country=fr&future-filter=arg

You could even do /stats?yesterday. Paths are for hierarchical data, query params for key-value data

Routes are compiled so I don’t think something like Rails’ regex-based constraints could ever be possible. I also don’t see a big difference between params: %{country: country} and your live action approach.

I agree with @thiagomajesk that having sub routes is the way to go, but if you really don’t want to, I would make live components for each stat type and delegate in the router:

def render(%{param: param} = assigns) when param in @countries do
  ~H"""
  <.live_component id="countries" module={MyAppWeb.CountryStatsComponent} countries={@countries} />
  """
end

def render(assigns) do
  ~H"""
  <.live_component id="range" module={MyAppWeb.RangeStatsComponent} ranges={@ranges} />
  """
end

That’s just a high-level example and I’m leaving out some context—there are several ways you could accomplish this.