fix(signature-collection): remove tooltip

[albinagu]

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Formatting passes locally with my changes
• I have rebased against main before asking for a review

Summary by CodeRabbit

• New Features

  • Improved tooltip placement for the supervisors section in the OwnerView component, now displayed at the bottom for better visibility.
  • Updated tooltip placement in the PaperSignees component for enhanced user experience.

• Bug Fixes

  • Removed tooltip color to streamline the interface.

[coderabbitai]

Walkthrough

The pull request modifies the OwnerView and PaperSignees components. Specifically, the tooltip placement for both components has been changed from "right" to "bottom," and the tooltip color has been removed from the OwnerView component. These adjustments affect the visual presentation of the tooltips while maintaining the components' existing functionality and structure.

Changes

File	Change Summary
libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/ViewList/Signees/PaperSignees.tsx	Modified tooltip placement from "right" to "bottom".
libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/index.tsx	Changed tooltip placement from "right" to "bottom" and removed tooltip color.

Possibly related PRs

• feat(service-portal): Parliamentary setup #15451: The changes in the OwnerView component are related as they both involve modifications to the same file and enhance the user interface for managing parliamentary lists.
• fix(signature-collection): cleanup constituencies #15864: This PR also modifies the OwnerView component, specifically removing sections related to managers, which aligns with the changes made in the main PR regarding the tooltip and overall structure.
• fix(service-portal): owner view iteration #16038: The updates in this PR to the OwnerView component further streamline its functionality, which is relevant to the changes made in the main PR.
• fix(service-portal): owner UI updates + paper signees #16067: This PR introduces updates to the OwnerView component, which includes enhancements that are related to the changes made in the main PR.
• fix(service-portal): signature collection paper signees tweak #16108: The modifications in the PaperSignees component are relevant as they involve similar functionality related to the signature collection process.
• fix(signature-collection): tweaks 15.10 #16402: The changes in the OwnerView component regarding tooltip updates are directly related to the modifications made in the main PR.
• fix(signature-collection): Tweaks for parliamentary collection #16407: This PR includes updates to the OwnerView component that enhance its functionality, which is relevant to the changes made in the main PR.
• fix(signature-collection): refetch is owner 16.10 #16432: The addition of the refetchIsOwner prop in the OwnerView component is relevant as it enhances the functionality of the component, similar to the changes made in the main PR.

Suggested reviewers

• kksteini
• juni-haukur

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between efe3a71 and 93821aa.

📒 Files selected for processing (1)

• libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/index.tsx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/index.tsx

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/index.tsx (1)

208-210: LGTM! Consider adding a responsive placement.

The change from "right" to "bottom" placement for the Tooltip is a good improvement, especially for responsive design. It aligns with the changes mentioned in the PR summary.

For even better responsiveness, consider using a dynamic placement based on screen size:

placement={['bottom', 'right']}

This will use "bottom" placement on smaller screens and "right" on larger ones, ensuring optimal visibility across devices.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 695edee and efe3a71.

📒 Files selected for processing (2)

• libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/ViewList/Signees/PaperSignees.tsx (1 hunks)
• libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/index.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/ViewList/Signees/PaperSignees.tsx

🧰 Additional context used

📓 Path-based instructions (1)

libs/service-portal/signature-collection/src/screens/Parliamentary/OwnerView/index.tsx (1)

Pattern libs/**/*: "Confirm that the code adheres to the following:

• Reusability of components and hooks across different NextJS apps.
• TypeScript usage for defining props and exporting types.
• Effective tree-shaking and bundling practices."