From 4c377eab14460655addafa128cdee5da5b85ea53 Mon Sep 17 00:00:00 2001 From: Christopher Hamilton Date: Mon, 11 Feb 2019 17:55:37 +0000 Subject: [PATCH] docs: CSS modules class name reference fix (2lRF7) (#11694) The image and the text showing the value of the Avatar key do not currently match. --- docs/tutorial/part-two/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/part-two/index.md b/docs/tutorial/part-two/index.md index b837d0b128ad8..c38097c23399a 100644 --- a/docs/tutorial/part-two/index.md +++ b/docs/tutorial/part-two/index.md @@ -254,7 +254,7 @@ The `console.log(styles)` code will log the resulting import so you can see the ![css-modules-console](css-modules-console.png) If you compare that to your CSS file, you'll see that each class is now a key in the imported object pointing to a long string e.g. `avatar` points to -`about-css-modules-module---avatar----hYcv`. These are the class names CSS +`src-pages----about-css-modules-module---avatar---2lRF7`. These are the class names CSS Modules generates. They're guaranteed to be unique across your site. And because you have to import them to use the classes, there's never any question about where some CSS is being used.