feat(18342): add bio tooltip v2

[Natallia-Harshunova]

https://kontur.fibery.io/Tasks/Task/Add-bio-tooltip-18342

Summary by CodeRabbit

• New Features

  • Introduced a tooltip feature for the biography text area in the user profile settings, providing additional information when clicked.

• Style

  • Added a new CSS class for tooltip content styling and made adjustments to spacing and alignment.

[coderabbitai]

Walkthrough

The recent updates enhance the user biography section within the SettingsForm component. The key update involves replacing the placeholder text with a tooltip that provides additional guidance when a user interacts with the text area. This change includes updates to the translation keys, introduction of new CSS classes for tooltip styling, and the implementation of tooltip logic in the React component.

Changes

Files / Changes	Summary
src/core/localization/translations/en/common.json	Key user_bio_placeholder updated to user_bio_tooltip.
src/features/user_profile/components/SettingsForm/SettingsForm.module.css	Added .bioTooltipContent with white-space: pre-wrap; removed .textAreaPlaceholder with white-space: pre-wrap; minor spacing and alignment adjustments.
src/features/user_profile/components/SettingsForm/SettingsForm.tsx	Introduced tooltip functionality for the biography text area, including state management for tooltip display and corresponding event handling.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TextArea
    participant Tooltip
    User->>TextArea: Click
    TextArea->>Tooltip: Toggle visibility
    Tooltip-->>User: Display additional info

Loading

Poem

In the lands where code does roam,
A tooltip rose from lines of chrome.
The bio's hint, now clear as day,
Guides the user on their way.
With CSS and hooks so spry,
The SettingsForm now reaches high.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[github-actions]

Language	To Recheck	Fuzzy	Untranslated	Total
ar	3	24	101	128
de	2	24	101	127
es	3	24	101	128
id	2	24	101	127
ko	3	24	101	128
uk	0	7	8	15

[github-actions]

Bundle size diff

Old size	New size	Diff
4.91 MB	4.91 MB	601 B (0.01%)

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 60b43bb and 1d7eb71.

Files selected for processing (3)

• src/core/localization/translations/en/common.json (1 hunks)
• src/features/user_profile/components/SettingsForm/SettingsForm.module.css (2 hunks)
• src/features/user_profile/components/SettingsForm/SettingsForm.tsx (4 hunks)

Files not reviewed due to errors (1)

• src/features/user_profile/components/SettingsForm/SettingsForm.tsx (no review received)

Additional comments not posted (6)

src/features/user_profile/components/SettingsForm/SettingsForm.module.css (5)

18-20: CSS class addition approved.

The new .bioTooltipContent class with white-space: pre-wrap property is correctly implemented. This will ensure that the formatting of the tooltip text is maintained as expected.

---

Line range hint 4-4: Review of new imports and tooltip components.

The addition of useEffect, useRef, useState from React, and Tooltip, TooltipTrigger, TooltipContent from '~core/tooltips' are appropriate for the feature being implemented. These imports are necessary for the tooltip functionality and managing its state.

Also applies to: 12-12

---

Line range hint 45-47: State and ref initialization for tooltip functionality.

The usage of useState for managing the tooltip's visibility and useRef for referencing the biography text area is correctly implemented. This setup is essential for controlling the tooltip display based on user interactions.

---

Line range hint 66-79: Review of useEffect for handling outside click to close tooltip.

The useEffect hook setup for adding and removing event listeners based on the tooltip's visibility state is well-implemented. This ensures that the tooltip is closed when a click occurs outside of the referenced element.

---

Line range hint 139-165: Implementation of the Tooltip component.

The Tooltip component is correctly implemented with appropriate triggers and content. The use of onMouseDown, onFocus, and onBlur event handlers to control the tooltip's visibility is a good practice, ensuring that the tooltip behaves as expected across different user interactions.

src/core/localization/translations/en/common.json (1)

366-367: Localization key update approved.

The renaming of user_bio_placeholder to user_bio_tooltip and the update of its description are correctly implemented. This change is consistent with the PR objectives to enhance the tooltip functionality in the user profile settings.