From 6c4569656f123394c0475c81255e9059003f2be4 Mon Sep 17 00:00:00 2001
From: Matt Dunn-Rankin <mattdunnrankin@khanacademy.org>
Date: Sat, 2 May 2020 23:32:45 -0700
Subject: [PATCH] try to fix a compiler bug?

It looks like, in prod, our lambda fn here got optimized away, and I'm guessing it's because it starts with a comment now? I moved the comment down a line, fingers crossed!
---
 src/app/OutfitPreview.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/app/OutfitPreview.js b/src/app/OutfitPreview.js
index b1c7e946..613d70aa 100644
--- a/src/app/OutfitPreview.js
+++ b/src/app/OutfitPreview.js
@@ -43,9 +43,9 @@ export function OutfitLayers({ loading, visibleLayers, doAnimations = false }) {
     <Box pos="relative" height="100%" width="100%">
       <TransitionGroup enter={false} exit={doAnimations}>
         {visibleLayers.map((layer) => (
-          // We manage the fade-in and fade-out separately! The fade-out
-          // happens here, when the layer exits the DOM.
           <CSSTransition
+            // We manage the fade-in and fade-out separately! The fade-out
+            // happens here, when the layer exits the DOM.
             key={layer.id}
             classNames={css`
               &-exit {