Browse code
Fix indentation, ignore compilation artifacts
Ed Langley authored on 18/06/2017 05:23:10
Showing 3 changed files
Showing 3 changed files
... | ... |
@@ -36,12 +36,12 @@ const store = createStore(reduce, compose( |
36 | 36 |
enhance, |
37 | 37 |
applyMiddleware(middleware) |
38 | 38 |
)); |
39 |
-</code></pre><p>Any time a handled action fires the url in the address bar will change, and if the url in the address bar changes the corresponding action will fire (unless the action was initiated by a url change).</p><h2 id="route-matching-precedence---which-route-matches-best">Route matching precedence - which route matches best?</h2><p>Route precedence is a function of the type of matching done in each segment and the order in which the wildcard segments match. Exact matches are always preferred to wildcards moving from left to right.</p><pre class="brush: javascript"><code> const routesInOrderOfPrecedence = [ |
|
40 |
- ['/user/me/update', '/user/me'], // both perfectly specific - will match above any wildcard route |
|
41 |
- '/user/me/:view', |
|
42 |
- '/user/:id/update', // less specific because 'me' is exact match, while :id is a wildcard |
|
43 |
- '/user/:id/:view' |
|
44 |
- ]; |
|
39 |
+</code></pre><p>Any time a handled action fires the url in the address bar will change, and if the url in the address bar changes the corresponding action will fire (unless the action was initiated by a url change).</p><h2 id="route-matching-precedence---which-route-matches-best">Route matching precedence - which route matches best?</h2><p>Route precedence is a function of the type of matching done in each segment and the order in which the wildcard segments match. Exact matches are always preferred to wildcards moving from left to right.</p><pre class="brush: javascript"><code>const routesInOrderOfPrecedence = [ |
|
40 |
+ ['/user/me/update', '/user/me'], // both perfectly specific - will match above any wildcard route |
|
41 |
+ '/user/me/:view', |
|
42 |
+ '/user/:id/update', // less specific because 'me' is exact match, while :id is a wildcard |
|
43 |
+ '/user/:id/:view' |
|
44 |
+]; |
|
45 | 45 |
</code></pre><h2 id="fragment-component">Fragment component</h2><pre class="brush: javascript"><code> |
46 | 46 |
const state = { |
47 | 47 |
menu: ... |
... | ... |
@@ -86,12 +86,12 @@ Route precedence is a function of the type of matching done in each segment and |
86 | 86 |
match. Exact matches are always preferred to wildcards moving from left to right. |
87 | 87 |
|
88 | 88 |
```javascript |
89 |
- const routesInOrderOfPrecedence = [ |
|
90 |
- ['/user/me/update', '/user/me'], // both perfectly specific - will match above any wildcard route |
|
91 |
- '/user/me/:view', |
|
92 |
- '/user/:id/update', // less specific because 'me' is exact match, while :id is a wildcard |
|
93 |
- '/user/:id/:view' |
|
94 |
- ]; |
|
89 |
+const routesInOrderOfPrecedence = [ |
|
90 |
+ ['/user/me/update', '/user/me'], // both perfectly specific - will match above any wildcard route |
|
91 |
+ '/user/me/:view', |
|
92 |
+ '/user/:id/update', // less specific because 'me' is exact match, while :id is a wildcard |
|
93 |
+ '/user/:id/:view' |
|
94 |
+]; |
|
95 | 95 |
|
96 | 96 |
``` |
97 | 97 |
|