Fix incorrect condition in "Chains of computations" example

[PaulyBearCoding]

Fixes #8097

Problem

In the "Chains of computations" section, the refactored example uses an incorrect condition that changes the game logic from the original:

// Current (incorrect)
if (goldCardCount <= 3) {
  setGoldCardCount(goldCardCount + 1);
} else {
  // advance round
}

This allows 5 gold cards before advancing the round, which differs from the original Effect-based example that advances after 4 gold cards.

Solution

Changed the condition from <= to <:

// Fixed
if (goldCardCount < 3) {
  setGoldCardCount(goldCardCount + 1);
} else {
  // advance round
}

Why This Fix is Correct

The original "bad" example increments first, then checks:

useEffect(() => {
  setGoldCardCount(c => c + 1);  // 0→1, 1→2, 2→3, 3→4
}, [card]);

useEffect(() => {
  if (goldCardCount > 3) {  // Triggers when count reaches 4
    setRound(r => r + 1);
    setGoldCardCount(0);
  }
}, [goldCardCount]);

This advances after 4 cards (when count reaches 4).

The fixed example checks before incrementing:

• With <= 3: Allows counts 0,1,2,3 to increment → 4 values → advances on 5th card ❌
• With < 3: Allows counts 0,1,2 to increment → 3 values → advances on 4th card ✅

Testing

Verified the fix by:

1. Tracing execution logic step-by-step
2. Building the docs site locally and confirming correct rendering
3. Checking that only the intended line was modified

Changes

• File: src/content/learn/you-might-not-need-an-effect.md
• Line: 440
• Change: goldCardCount <= 3 → goldCardCount < 3

[meta-cla]

Hi @PaulyBearCoding!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[github-actions]

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌