{"files":[{"status":"M","path":"docs\/_data\/nav_docs.yml"},{"status":"M","path":"docs\/docs\/11-advanced-performance.md"},{"status":"A","path":"docs\/docs\/12-context.md"}],"commit":{"revision":"4e48c67120513942d73bfce3f95562a2dc5e7e7c","authorEmail":"ben@benalpert.com","authorName":"Ben Alpert","authoredAt":"2015-10-09T14:46:56-07:00","subject":"Merge pull request #5113 from spicyj\/document-context","shortRevision":"4e48c67120"},"parents":["09b688efcefeb617919364cd3bce79ea51a36bc1","28b10a9d6a29e1ffe4496108331a212279159913"],"body":"Document context","patch":"diff --git a\/docs\/_data\/nav_docs.yml b\/docs\/_data\/nav_docs.yml\nindex 4c7524bb2f..5970733c92 100644\n--- a\/docs\/_data\/nav_docs.yml\n+++ b\/docs\/_data\/nav_docs.yml\n@@ -67,6 +67,8 @@\n title: Performance Tools\n - id: advanced-performance\n title: Advanced Performance\n+ - id: context\n+ title: Context\n - title: Reference\n items:\n - id: top-level-api\ndiff --git a\/docs\/docs\/11-advanced-performance.md b\/docs\/docs\/11-advanced-performance.md\nindex e85932213f..12e7c5b82c 100644\n--- a\/docs\/docs\/11-advanced-performance.md\n+++ b\/docs\/docs\/11-advanced-performance.md\n@@ -3,6 +3,7 @@ id: advanced-performance\n title: Advanced Performance\n permalink: advanced-performance.html\n prev: perf.html\n+next: context.html\n ---\n \n One of the first questions people ask when considering React for a project is whether their application will be as fast and responsive as an equivalent non-React version. The idea of re-rendering an entire subtree of components in response to every state change makes people wonder whether this process negatively impacts performance. React uses several clever techniques to minimize the number of costly DOM operations required to update the UI.\ndiff --git a\/docs\/docs\/12-context.md b\/docs\/docs\/12-context.md\nnew file mode 100644\nindex 0000000000..6b24d243c4\n--- \/dev\/null\n+++ b\/docs\/docs\/12-context.md\n@@ -0,0 +1,136 @@\n+---\n+id: context\n+title: Context\n+permalink: context.html\n+prev: advanced-performance.html\n+---\n+\n+One of React's biggest strengths is that it's easy to track the flow of data through your React components. When you look at a component, you can easily see exactly which props are being passed in which makes your apps easy to reason about.\n+\n+Occasionally, you want to pass data through the component tree without having to pass the props down manually at every level. React's \"context\" feature lets you do this.\n+\n+> Note:\n+>\n+> Context is an advanced and experimental feature. The API is likely to change in future releases.\n+>\n+> Most applications will never need to use context. Especially if you are just getting started with React, you likely do not want to use context. Using context will make your code harder to understand because it makes the data flow less clear. It is similar to using global variables to pass state through your application.\n+>\n+> **If you have to use context, use it sparingly.**\n+>\n+> Regardless of whether you're building an application or a library, try to isolate your use of context to a small area and avoid using the context API directly when possible so that it's easier to upgrade when the API changes.\n+\n+## Passing info automatically through a tree\n+\n+Suppose you have a structure like:\n+\n+```javascript\n+var Button = React.createClass({\n+ render: function() {\n+ return (\n+

dillon1000/react

Files changed