refactor: use successData from usePictoQuery in Home

[puneeth-92]

While reading through the Home page implementation, I noticed that the component was accessing data?.data directly even though usePictoQuery already exposes successData for this purpose.

This change updates the Home page to use successData instead, which better aligns with the abstraction provided by usePictoQuery and avoids the need for explicit casting in the component.

The behavior remains unchanged — images are still fetched, stored in Redux, and rendered in the gallery as before — but the code is now a bit cleaner and more consistent with the intended usage of the query hook.

Summary by CodeRabbit

• Refactor
  • Improved internal code quality and maintainability in the Home page component through updated variable naming and dependency management.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request renames a destructured query variable from data to successData in the Home component's usePictoQuery hook, updating all references in the conditional dispatch logic and the useEffect dependency array accordingly.

Changes

Cohort / File(s)	Summary
Variable Rename frontend/src/pages/Home/Home.tsx	Renames destructured query result from data to successData; updates dispatch condition and useEffect dependency array to use the new variable name

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A variable renamed from data to successData bright,
Makes the code's intent crystal, wonderfully right!
No logic has changed, just clarity's gleam,
A hop through the codebase, a refactoring dream! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: refactoring the Home component to use successData from usePictoQuery instead of data?.data.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a3af96c and c61790e.

📒 Files selected for processing (1)

• frontend/src/pages/Home/Home.tsx

🧰 Additional context used

🧬 Code graph analysis (1)

frontend/src/pages/Home/Home.tsx (2)

frontend/src/hooks/useQueryExtension.ts (1)

• usePictoQuery (80-108)

frontend/src/features/imageSlice.ts (1)

• setImages (18-20)

🔇 Additional comments (1)

frontend/src/pages/Home/Home.tsx (1)

25-25: LGTM! Clean refactoring that uses the hook's intended abstraction.

The changes correctly leverage successData from usePictoQuery instead of manually accessing data?.data, making the code more consistent with the hook's design. The refactoring:

• Properly destructures successData which is already typed as TSuccessData | undefined
• Maintains type safety with the ?? [] fallback for setImages
• Correctly updates the dependency array to reflect the new variable name

No behavioral changes—successData is derived from data?.data in the hook implementation, so the logic remains equivalent.

Also applies to: 43-43, 45-45

---

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.}

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[puneeth-92]

This is a small refactor I noticed while reading through the Home page code, and it isn’t tied to an existing issue.