fix: prevent state updates after unmount in chapters geoLocData fetch

[khushia3]

This PR prevents state updates after component unmount or effect re-run
in the chapters page by adding a safe cancellation pattern to the
geoLocData fetch.

Fixes #3670

[github-actions]

The linked issue must be assigned to the PR author.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary by CodeRabbit

• Bug Fixes
  • Enhanced reliability of data loading on the chapters page, addressing state management issues that could occur during page navigation.

Walkthrough

The PR adds a mounted ref guard to the chapters page's async data fetching effect. A useRef(true) tracks component mount status, toggled in the effect cleanup. The setGeoLocData state update now executes only when the component is mounted, preventing memory leak warnings and state updates on unmounted components.

Changes

Cohort / File(s)	Summary
Mounted Guard for Async Fetch frontend/src/app/chapters/page.tsx	Added isMountedRef to guard setGeoLocData against post-unmount state updates. Imported useEffect, useRef, and useState hooks; reorganized imports to place useSearchPage after React imports. Effect cleanup flips ref to false; API response handler checks ref before updating state.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Add precise location sharing option for chapter map #2644: Modifies the same frontend/src/app/chapters/page.tsx file and alters how geoLocData is passed to the ChapterMapWrapper component.

Suggested labels

frontend

Suggested reviewers

• arkid15r
• kasya

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud