fix : added cursor-pointer to signin button

[ishanBahuguna]

Proposed change

Added cursor-pointer to signin button in UserMenu component and added test

Resolves #2269

Checklist

• I've read and followed the contributing guidelines.
• I've run make check-test locally; all checks and tests passed.

[coderabbitai]

Summary by CodeRabbit

• Style
  • Improved the Sign In button’s hover behavior to display a pointer cursor, enhancing click affordance and visual feedback for unauthenticated users. No functional changes to navigation or authentication flow.
• Tests
  • Updated unit tests to reflect the revised button styling and ensure UI expectations remain accurate.

Walkthrough

Adds the CSS class "cursor-pointer" to the Sign In button in UserMenu and updates the corresponding unit test to expect this class. No functional logic changes.

Changes

Cohort / File(s)	Summary
UserMenu component frontend/src/components/UserMenu.tsx	Added "cursor-pointer" to Sign In button className in unauthenticated branch. No logic changes.
Unit tests frontend/__tests__/unit/components/UserMenu.test.tsx	Updated expectation to include "cursor-pointer" in class assertion for Sign In button.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• test: add unit tests for UserMenu component (#1918) #1948 — Modifies UserMenu tests; related because this PR updates UserMenu and its test expectations for CSS classes.

Suggested reviewers

• arkid15r
• kasya

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 PR title "fix : added cursor-pointer to signin button" accurately and concisely describes the main change (adding the cursor-pointer class to the Sign In button) and is directly related to the changeset.
Linked Issues Check	✅ Passed	The change implements the coding objective from the linked issue [#2269] by adding the cursor-pointer class to frontend/src/components/UserMenu.tsx and updating the corresponding unit test, which satisfies the issue requirement to show a pointer cursor for the Sign In button.
Out of Scope Changes Check	✅ Passed	Only the UserMenu component and its unit test were modified to add the cursor-pointer class and update expectations; no unrelated files, API signatures, or business logic were changed, so there are no detected out-of-scope changes.
Description Check	✅ Passed	The PR description states the implemented change (adding cursor-pointer to the UserMenu Sign In button), references resolving issue #2269, and notes that tests passed locally, so it is relevant and aligned with the changeset.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 20c8a99 and 4d0c368.

📒 Files selected for processing (2)

• frontend/__tests__/unit/components/UserMenu.test.tsx (1 hunks)
• frontend/src/components/UserMenu.tsx (1 hunks)

🔇 Additional comments (2)

frontend/src/components/UserMenu.tsx (1)

50-50: Cursor affordance added to Sign In — LGTM

Matches issue #2269 scope; no side effects observed.

frontend/__tests__/unit/components/UserMenu.test.tsx (1)

645-645: Test updated for cursor-pointer — LGTM

Assertion correctly checks for the new utility.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarQube Cloud

[kasya]

@ishanBahuguna Thanks for also updating the test 👍🏼