FriendsOfSymfony/FOSRestBundle — pull request #162 by asm89 (2011-12-14 15:49:39+00:00)
Title: Optional parameters should not end up in the routing for the resource

```plain
asm89 | i want an optional sort mode for this URI
asm89 | /threads/1234/comments.json
asm89 | RESTBundle puts it in the routing
lsmith | sort mode sounds like a GET parameter
asm89 | /threads/1234/comment/{sortmode?}.json
lsmith | asm89: no .. that isnt RESTful ..
asm89 | but you _have_ to put something in the sortmode field
asm89 | that's what i thought
lsmith | its the same resource .. just a different representation
asm89 | /threads/1234/comments.json?sort=foo
lsmith | yup
asm89 | /threads/1234/comments.json?sort=foo&displayDepth=42
lsmith | yuo
asm89 | so the route matching shouldn't change for non-default params
lsmith | yeah .. one route for all
lsmith | if you need to split it up because the logic is so different .. then split it inside the action
asm89 | agreed
```