From 18d43372230339097e4a4cc9f343681801c215dc Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Mon, 10 Feb 2020 15:45:38 +0100 Subject: [PATCH] Update about-the-lab.md --- docs/src/pages/components/about-the-lab/about-the-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/components/about-the-lab/about-the-lab.md b/docs/src/pages/components/about-the-lab/about-the-lab.md index 995c34fb1ff713..26db0e939758e6 100644 --- a/docs/src/pages/components/about-the-lab/about-the-lab.md +++ b/docs/src/pages/components/about-the-lab/about-the-lab.md @@ -7,7 +7,7 @@ The main difference between the lab and the core is how the components are versi As developers use and test the components and report issues, the maintainers learn more about shortcomings of the components: missing features, accessibility issues, bugs, API design, etc. The older and more used a component is, the less likely it is that new issues will be found and subsequently need to introduce breaking changes. For a component to be ready to move to the core, the following criteria are considered: -* It needs to be **used**. The Material UI team uses Google Analytics stats to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it. +* It needs to be **used**. The Material-UI team uses Google Analytics stats among other metrics to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it. * It needs to match the **code quality** of the core components. It doesn't have to be perfect to be a part of the core, but the component should be reliable enough that developers can depend on it. * Each component needs **type definitions**. It is not currently required that a lab component is typed, but it would need to be typed to move to the core. * Requires good **test coverage**. Some of the lab components don't currently have comprehensive tests.