From 406d6b352231a7b9960b7ec111e684965d0a6ff8 Mon Sep 17 00:00:00 2001 From: developer Date: Fri, 11 Jul 2025 11:53:25 +0300 Subject: [PATCH] fix(docs): prevent runtime error in a broken clock challenge by checking element existence --- src/content/learn/keeping-components-pure.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/content/learn/keeping-components-pure.md b/src/content/learn/keeping-components-pure.md index 70049e58e27..609c2fba8dc 100644 --- a/src/content/learn/keeping-components-pure.md +++ b/src/content/learn/keeping-components-pure.md @@ -246,11 +246,12 @@ Rendering is a *calculation*, it shouldn't try to "do" things. Can you express t ```js src/Clock.js active export default function Clock({ time }) { const hours = time.getHours(); - if (hours >= 0 && hours <= 6) { - document.getElementById('time').className = 'night'; - } else { - document.getElementById('time').className = 'day'; + const timeElement = document.getElementById('time'); + + if (timeElement) { + timeElement.className = hours >= 0 && hours <= 6 ? 'night' : 'day'; } + return (

{time.toLocaleTimeString()}