I don’t recall Phoenix ever supporting route constraints because you can just use pattern-matching to emulate the same behavior (although I agree it could be useful as it’s more explicit and allows for conditional dispatching). The way I’d go about this is just specifying different routes, so live "/stats/country/:country" and live "/stats/range/:range". You always have the option to keep using live actions and handle_params to handle constraints.
