You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for #6. corrects original issue, but breaks a feature
slogsdon
changed the title
router: "cannot match because a previous clause always matches" errors
router: need a better way to match on request extensions
Sep 15, 2014
Current dependence on Plug for route param parsing and Erlang's inability to pattern match binaries like param <> ".ext" makes this difficult to handle at compile time without rewriting a good amount of code.
Optimal solution at this point will probably be a plug to be early in the call stack, parsing the last captured param for an extension/MIME-type, setting Accept header, and removing the extension
caused by a route path with a capture and an extension at end of path.
Example:
The text was updated successfully, but these errors were encountered: