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
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ thought, not an after-thought.
18
18
-[Changelog](/CHANGELOG.md)
19
19
-[#react-router channel on reactiflux](http://www.reactiflux.com/)
20
20
21
+
**Note:***If you are still using React Router 0.13.x [the docs](https://github.com/rackt/react-router/tree/0.13.x/docs/guides) can be found on [the 0.13.x branch](https://github.com/rackt/react-router/tree/0.13.x).*
22
+
21
23
### Browser Support
22
24
23
25
We support all browsers and environments where React runs.
After updating to 1.0.0 you will notice that a magic querystring entry starts appearing in your URLs called "_k". An example of how it looks is this: `?_k=umhx1s`.
59
+
60
+
This is not a bug - this is intended. You can read more about the feature [here](https://github.com/rackt/react-router/blob/master/docs/guides/basics/Histories.md#what-is-that-_kckuvup-junk-in-the-url) and how to opt out [here](https://rackt.github.io/history/stable/HashHistoryCaveats.html).
61
+
58
62
### Route Config
59
63
60
64
You can still nest your routes as before, paths are inherited from
@@ -116,11 +120,11 @@ since it's simple with a `*` path.
116
120
#### "active" class
117
121
118
122
In 0.13.x links added the "active" class by default which you could
119
-
override with `activeClassName`, or provide `activeStyles`. Most links
123
+
override with `activeClassName`, or provide `activeStyle`s. Most links
120
124
don't need this and the check is (currently) expensive.
121
125
122
126
Links no longer add the "active" class by default, you opt-in by
123
-
providing one; if no `activeClassName` or `activeStyles` are provided,
127
+
providing one; if no `activeClassName` or `activeStyle`s are provided,
For data loading, you can use the `renderProps` argument to build whatever
42
-
convention you want--like adding static `load` methods to your route
43
-
components, or putting data loading functions on the routes, it's up to
44
-
you.
38
+
For data loading, you can use the `renderProps` argument to build whatever convention you want--like adding static `load` methods to your route components, or putting data loading functions on the routes--it's up to you.
0 commit comments