summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPreston Parry <ClimbsRocks@users.noreply.github.com>2015-01-04 23:15:30 -0800
committerPreston Parry <ClimbsRocks@users.noreply.github.com>2015-01-04 23:15:30 -0800
commitbe4a6a6b02e935f01054785a0937be41e3bbf002 (patch)
tree9f2215ebc143e020f3db24228ce78874b4a0fdc6
parent631058b4642b2c2c3a852d21d18413a1eafadd62 (diff)
downloadbackbonetutorials-be4a6a6b02e935f01054785a0937be41e3bbf002.zip
backbonetutorials-be4a6a6b02e935f01054785a0937be41e3bbf002.tar.gz
backbonetutorials-be4a6a6b02e935f01054785a0937be41e3bbf002.tar.bz2
Escaped all asterisks within text
-rw-r--r--_posts/2011-01-27-what-is-a-router.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/_posts/2011-01-27-what-is-a-router.md b/_posts/2011-01-27-what-is-a-router.md
index 95f283a..90e32da 100644
--- a/_posts/2011-01-27-what-is-a-router.md
+++ b/_posts/2011-01-27-what-is-a-router.md
@@ -76,11 +76,11 @@ Most conventional frameworks allow you to define routes that contain a mix of st
_Notice the change in the url_
-## Dynamic Routing Cont. ":params" and "*splats"
+## Dynamic Routing Cont. ":params" and "\*splats"
-Backbone uses two styles of variables when implementing routes. First there are ":params" which match any URL components between slashes. Then there are "\*splats" which match any number of URL components. Note that due to the nature of a "*splat" it will always be the last variable in your URL as it will match any and all components.
+Backbone uses two styles of variables when implementing routes. First there are ":params" which match any URL components between slashes. Then there are "\*splats" which match any number of URL components. Note that due to the nature of a "\*splat" it will always be the last variable in your URL as it will match any and all components.
-Any "*splats" or ":params" in route definitions are passed as arguments (in respective order) to the associated function. A route defined as "/:route/:action" will pass 2 variables (“route” and “action”) to the callback function. (If this is confusing please post a comment and I will try articulate it better)
+Any "\*splats" or ":params" in route definitions are passed as arguments (in respective order) to the associated function. A route defined as "/:route/:action" will pass 2 variables (“route” and “action”) to the callback function. (If this is confusing please post a comment and I will try articulate it better)
Here are some examples of using ":params" and "*splats"