feat: include game monitor type in status page monitor selection

[TudorGR]

(Please remove this line only before submitting your PR. Ensure that all relevant items are checked before submission.)

Describe your changes

• Include the “game” monitor type in the Status Page monitor selection.
• Change is limited to the client hook client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx, adding "game" to the types filter so game servers can be added to a status page.
• No backend changes. UI remains the same; the Status Page “Contents” monitor picker now shows game monitors.
• Screenshot attached in the PR demonstrating that “Game” appears and works in the monitor type selection.

Write your issue number after "Fixes "

Fixes #3048

Please ensure all items are checked off before requesting a review. "Checked off" means you need to add an "x" character between brackets so they turn into checkmarks.

• (Do not skip this or your PR will be closed) I deployed the application locally.
• (Do not skip this or your PR will be closed) I have performed a self-review and testing of my code.
• I have included the issue # in the PR.
• I have added i18n support to visible strings (instead of <div>Add</div>, use):

const { t } = useTranslation();
<div>{t('add')}</div>

• I have not included any files that are not related to my pull request, including package-lock and package-json if dependencies have not changed
• I didn't use any hardcoded values (otherwise it will not scale, and will make it difficult to maintain consistency across the application).
• I made sure font sizes, color choices etc are all referenced from the theme. I don't have any hardcoded dimensions.
• My PR is granular and targeted to one specific feature.
• I ran npm run format in server and client directories, which automatically formats your code.
• I took a screenshot or a video and attached to this PR if there is a UI change.

Summary by CodeRabbit

• New Features
  • Added support for "game" monitor type in status page creation. Users can now select from http, ping, port, and game monitor types when configuring status pages.

[coderabbitai]

Walkthrough

A single file modified to include the "game" monitor type in the status page monitor selection, expanding the array from three monitor types to four.

Changes

Cohort / File(s)	Summary
Monitor type expansion client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx	Added "game" to the monitor types array passed to getMonitorsByTeamId, enabling game server monitors in status page creation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

No complex logic changes or structural modifications present. This is a straightforward addition of a string literal to an existing array.

Poem

🐰 A rabbit hops through code so neat,
Adding "game" to monitors sweet,
Status pages now complete,
With server checks—what a treat! 🎮

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "feat: include game monitor type in status page monitor selection" clearly and specifically describes the main change in the changeset. It directly relates to the code modification, which adds "game" to the monitor types filter in the useMonitorsFetch hook. The title is concise, meaningful, and uses standard conventional commit formatting. It conveys enough information for developers scanning the history to immediately understand the primary change without being vague or generic.
Linked Issues Check	✅ Passed	The linked issue #3048 requires adding the game server monitor type to the list of monitors in status pages. The PR successfully fulfills this requirement by modifying the useMonitorsFetch hook to include "game" in the monitor types array, expanding the selection from ["http", "ping", "port"] to ["http", "ping", "port", "game"]. The screenshot provided in the description confirms that game monitors now appear in the status page monitor picker, directly addressing the objective stated in the linked issue.
Out of Scope Changes Check	✅ Passed	The changeset is highly focused and targeted to a single file modification with no out-of-scope changes. Only client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx has been modified, and the only alteration is the addition of "game" to the monitor types array. No unrelated files, dependencies, logic restructuring, or other changes are present. The modification is minimal, precise, and entirely scoped to the requirement of including the game monitor type in status page selection.
Description Check	✅ Passed	The pull request description follows the repository template comprehensively. It includes a clear description of the changes explaining the purpose of adding "game" to the monitor types filter, specifies the exact file modified, and links the issue number (#3048). All pre-submission checklist items are properly checked off, indicating the author has verified local deployment, performed self-review and testing, ensured i18n support, and provided supporting evidence through an attached screenshot. The description demonstrates that all required and recommended practices were followed.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7fb4e75 and d2ff386.

📒 Files selected for processing (1)

• client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-07-24T17:52:55.506Z

Learnt from: Jesulayomy
PR: bluewave-labs/Checkmate#2664
File: client/src/Pages/Uptime/Create/index.jsx:92-96
Timestamp: 2025-07-24T17:52:55.506Z
Learning: In the Uptime monitor components, the `formatAndSet` function was deprecated due to rendering issues caused by state mutations. The current approach stores intervals internally in milliseconds (API format) but converts for display using `const displayInterval = monitor?.interval / MS_PER_MINUTE || 1;` and converts user input back to milliseconds using `value = value * MS_PER_MINUTE` in the onChange handler.

Applied to files:

• client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx

🔇 Additional comments (1)

client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx (1)

17-17: Change approved. Verification confirms backend support and intentional design.

The addition of "game" to the status page monitor types is complete and correct. Backend validation, models, and database queries all properly support the "game" monitor type. The maintenance hook intentionally uses a different type set ("pagespeed" instead of "game"), reflecting different feature requirements—this is appropriate and requires no changes.

---

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

[llamapreview]

AI Code Review by LlamaPReview

🎯 TL;DR & Recommendation

Recommendation: Approve with suggestions

This PR successfully adds game monitor support to status pages with minor maintainability and documentation suggestions for future improvements.

🌟 Strengths

• Implements the requested feature cleanly without backend changes.
• Well-scoped change with no critical issues.

💡 Suggestions (P2)

• client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx: Hardcoded monitor types array could lead to inconsistencies if new types are added without updates here.
• client/src/Pages/v1/StatusPage/Create/Hooks/useMonitorsFetch.jsx: The modified comment omits original context, potentially confusing future developers about supported monitor types.

---

💡 Have feedback? We'd love to hear it in our GitHub Discussions.
✨ This review was generated by LlamaPReview Advanced, which is free for all open-source projects. Learn more.

[llamapreview]

P2 | Confidence: High

• The hardcoded array of monitor types creates maintenance risk, as future additions would require manual updates across multiple locations, potentially leading to inconsistencies. Consider defining monitor types in a shared constants file for better maintainability.
• The updated comment removes previous context about supported monitor types, reducing clarity for future maintainers. Suggest updating the comment to include all supported types for better documentation.