parameters. So you would need to list every possible path. routes: "" : "defaultFunction" "page/:page" : "pageFunction" "filters/:filter" : "filtersFunction" "sort/:sort" : "sortFunction" "filters/:filter/page/:page" : "filtersPageFunction" "filters/:filter/sort/:sort" : "filtersSortFunction" "filters/:filter/sort/:sort/page/:page" : "allFunction" "sort/:sort/page/:page" : "sortPageFunction" Sunday, March 17, 13
view changes itself, then informs the router to update the route silently B. The view tells the router to trigger, upon that, the router tells the view to re-render Sunday, March 17, 13
at a certain state in your application: A.The user loads /my-app and then does something to change the route to /my-app#my/route B. The user loads /my-app#my/route directly Sunday, March 17, 13
flow for both scenarios: 1. A route change is triggered (either via page load or user interaction - it doesn't matter) 2. In response the router then tells the views to update accordingly Sunday, March 17, 13
(via page load) 2. In response the router then tells the views to update accordingly 1. A user interaction causes a view to change itself 2. The view then updates the route silently Sunday, March 17, 13
for: • Default Values (Which we already covered) • Parameter Groups (Setting one clears the others) • Required Params (If not set, no params are passed) • Tokens (aka flags, params without values) • Arrays (they can be appended to, uniqued, and more) Sunday, March 17, 13