Replace react-tooltip with AppTooltip in PullRequestItem

[bohdansolovie]

Summary

Replaces react-tooltip with AppTooltip from twenty-ui/display in the PullRequestItem component.

Changes

• ✅ Removed react-tooltip import
• ✅ Removed unused StyledTooltip styled component
• ✅ Added AppTooltip import from twenty-ui/display
• ✅ Updated component to use AppTooltip

Motivation

This addresses the TODO comment in the file and ensures consistency by using the shared UI component from twenty-ui instead of directly importing from react-tooltip.

AppTooltip is a styled wrapper around react-tooltip that provides consistent theming and styling across the application.

[github-actions]

Welcome!

Hello there, congrats on your first PR! We're excited to have you contributing to this project.
By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement.

TODOs/FIXMEs:

• // TODO: use twenty-ui Tooltip: packages/twenty-website/src/app/_components/contributors/PullRequestItem.tsx

Generated by 🚫 dangerJS against 8eac08c

[cubic-dev-ai]

No issues found across 1 file

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates packages/twenty-website/src/app/_components/contributors/PullRequestItem.tsx to stop importing react-tooltip directly and instead use the shared AppTooltip component from twenty-ui/display for the date tooltip.

The change centralizes tooltip styling/theming via twenty-ui, but the tooltip anchor is still selected via a DOM id derived only from prNumber (parsed from the PR URL). If duplicate PR numbers can appear in the same rendered page, the anchor id/anchorSelect pairing will collide and the tooltip may attach to the wrong element.

Confidence Score: 4/5

• Generally safe to merge once the tooltip anchor uniqueness concern is addressed/confirmed.
• The change is small and localized (tooltip wrapper swap), but the current anchorSelect targets an id derived only from prNumber, which can break tooltip targeting if duplicate values render on the same page.
• packages/twenty-website/src/app/_components/contributors/PullRequestItem.tsx

Important Files Changed

Filename	Overview
packages/twenty-website/src/app/_components/contributors/PullRequestItem.tsx	Replaces react-tooltip Tooltip/styled wrapper with AppTooltip from twenty-ui/display for date tooltip rendering; need to verify anchorSelect id uniqueness in list contexts and ensure AppTooltip is compatible with Next.js rendering for this component.

Sequence Diagram

sequenceDiagram
  participant PRList as PullRequests (list)
  participant Item as PullRequestItem
  participant Anchor as span#date-<key>
  participant Tooltip as AppTooltip

  PRList->>Item: render(props: {id,url,createdAt,mergedAt,...})
  Item->>Item: prNumber = last segment of url
  Item->>Anchor: render id="date-${prNumber}" with relative date
  Item->>Tooltip: render AppTooltip(anchorSelect="#date-${prNumber}")
  Tooltip->>Anchor: querySelector(anchorSelect)
  Tooltip-->>PRList: tooltip anchored to matched element

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[bohdansolovie]

Hello, @charlesBochet
Can you review this PR please?

Thanks

[charlesBochet]

@bohdansolovie Have you tried it?

Closing...

[bohdansolovie]

Hi, @charlesBochet
I tested it. I think this is an edge case.
Can you reopen this PR so that I can fix it?

[charlesBochet]

Ok, please add a screenshot in this case :)
To give you some context, we are getting a lot if IA PRs these days without people actually taking the time to think about it and to test it.
As a result, the core team is losing time to help people that are not really trying to help, which is not helping

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Tooltip anchor id collision

id={date-${prNumber}} is only derived from the PR number, so if this component is ever rendered with duplicate prNumber values on the same page, the HTML id will be duplicated and anchorSelect={#date-${prNumber}} will bind to the first matching element (wrong tooltip target). Consider including a guaranteed-unique value (e.g. id prop) in both the id and anchorSelect.