on SO by @chrismccord about pleasant pattern-matching request format on controller actions, followed by a few comments saying that it does not work. Well - I checked - it doesn’t. A suggestion of digging into private fields of conn instead unfortunately seems far less elegant. I assume this particular answer’s author knew what he was talking about In such case the param must have been removed at some point. And yes, I can imagine valid reasons for this removal but would like to know a) what was the actual rationale, and b) if there’s any replacement for this, other than mentioned in the comments to the answer (conn/private/phoenix_format) that could be used to pattern-match on controller actions?
Right. In such case I could “massage” whatever’s passed down to actions as I see fit and problem solved. OTOH it feels a bit like wrestling with the framework rather than working with it – you know what I mean? It’s probably the most flexible way though.