From a93ce64ca64a02513f1c00ab5a16d788c1e93d31 Mon Sep 17 00:00:00 2001 From: Cheng Lou Date: Tue, 24 Feb 2015 15:22:25 -0500 Subject: [PATCH] [Blog] Fix post code snippet display I think nokogiri (is that what we use?) accidentally escaped this snippet. Simply putting spaces between braces fixes it. --- _posts/2015-02-24-streamlining-react-elements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2015-02-24-streamlining-react-elements.md b/_posts/2015-02-24-streamlining-react-elements.md index 87bc81b5..98d9206b 100644 --- a/_posts/2015-02-24-streamlining-react-elements.md +++ b/_posts/2015-02-24-streamlining-react-elements.md @@ -162,7 +162,7 @@ In 0.13 we introduced a new callback-refs API that doesn’t suffer from these p In React 0.12, and earlier, you could use keyed objects to provide an external key to an element or a set. This pattern isn’t actually widely used. It shouldn’t be an issue for most of you. ```js -
{{ a: , b: }}
+
{ {a: , b: } }
``` ### Problem: Relies on Enumeration Order