{"body":"* Update context example for react-router@4.0.0-beta.1\r\n\r\n* Style nits","commit":{"revision":"564fa646262300683e2c0212fe12bcb0ae5e7daf","authoredAt":"2017-01-30T09:36:47-08:00","authorEmail":"mjijackson@gmail.com","subject":"Update context example for react-router v4 beta (#8889)","shortRevision":"564fa64626","authorName":"MICHAEL JACKSON"},"parents":["d8491ca73f4203a02973144ee6c518a8d3206800"],"files":[{"status":"M","path":"docs\/docs\/context.md"}],"patch":"diff --git a\/docs\/docs\/context.md b\/docs\/docs\/context.md\nindex 3ae11fe8b1..c5703d3545 100644\n--- a\/docs\/docs\/context.md\n+++ b\/docs\/docs\/context.md\n@@ -108,9 +108,11 @@ If `contextTypes` is not defined, then `context` will be an empty object.\n \n ## Parent-Child Coupling\n \n-Context can also let you build an API where parents and children communicate. For example, one library that works this way is [React Router V4](https:\/\/react-router.now.sh\/basic):\n+Context can also let you build an API where parents and children communicate. For example, one library that works this way is [React Router V4](https:\/\/reacttraining.com\/react-router):\n \n ```javascript\n+import { Router, Route, Link } from 'react-router-dom';\n+\n const BasicExample = () => (\n \n

\n@@ -120,17 +122,17 @@ const BasicExample = () => (\n

Topics<\/Link><\/li>\n <\/ul>\n \n- \n+

\n \n- \n- \n- \n+ \n+ \n+ \n <\/div>\n <\/Router>\n-)\n+);\n ```\n \n-By passing down some information from the `Router` component, each `Link` and `Match` can communicate back to the containing `Router`.\n+By passing down some information from the `Router` component, each `Link` and `Route` can communicate back to the containing `Router`.\n \n Before you build components with an API similar to this, consider if there are cleaner alternatives. For example, you can pass entire React component as props if you'd like to.\n \n"}

dillon1000/react

Files changed