Add tooltips and update uv.lock after installing pytest

[Likhitha-talent]

This PR adds helpful tooltips to the member form fields and buttons to improve user guidance and clarity:

who_area – "Describe who this member is (short bio)"

python_area – "Describe their experience with Python"

contributions_area – "List their contributions or achievements"

availability_area – "Mention when they are available (e.g., weekends)"

add_social_button – "Add a new social link"

add_alias_button – "Add a new alias"

save_button – "Save this member's profile"

back_button – "Go back to the members list without saving"

quit_button – "Exit the app"

Additionally, uv.lock has been updated after installing pytest to ensure dependencies are consistent.

This contribution addresses a good first issue by improving the usability and documentation of the member form.

Issue Reference:
Closes/Fixes #12

Summary by CodeRabbit

• New Features
  • Added contextual tooltips across the member editor to guide data entry and navigation.
  • Member list: tooltips for selecting files and creating profiles.
  • Profile form: tooltips for name, email, city, homepage, bio, Python experience, contributions, availability.
  • Social and alias sections: tooltips for adding, entering, and deleting items.
  • Action buttons: save, back, and quit now include descriptive hints.
  • No behavioral changes; existing workflows remain the same.

[coderabbitai]

Walkthrough

Added descriptive tooltip text to many UI widgets in src/edit_python_pe/main.py (inputs, buttons, list view, and text areas) to provide inline hints; no behavioral, navigation, event-handling, or public API/signature changes.

Changes

Cohort / File(s)

Change Summary

UI tooltip additions src/edit_python_pe/main.py

Added tooltips to SocialEntry (url_input, delete_btn), AliasEntry (alias_input, delete_btn), MemberApp.on_mount controls (list_view, add_list_button) and form fields/buttons (name_input, email_input, city_input, homepage_input, who_area, python_area, contributions_area, availability_area, add_social_button, add_alias_button, save_button, back_button, quit_button). No control-flow, error-handling, or public API changes.

Sequence Diagram(s)

(omitted — changes are UI tooltip metadata only; no control-flow modifications to diagram)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Select value was not populated on initialization #28 — Adds tooltip text to the same UI components (SocialEntry, AliasEntry, form inputs) and touches the same code-level UI elements; likely closely related.

Poem

I twitch my nose at hints so bright,
Little bubbles guide the night.
Hover here, a whisper shows,
Where to click and where to pose.
A rabbit's cheer for tiny light—tooltips snug and just right. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Linked Issues Check	⚠️ Warning	The pull request does not fulfill issue #12 because it fails to centralize user-facing strings into a separate module; instead, it introduces multiple hardcoded tooltip strings directly in the code and does not consolidate any existing literals into a shared resource.	Refactor the code to move all tooltip and other user-facing text into a dedicated strings module and update references accordingly to satisfy the requirements of issue #12.
Out of Scope Changes Check	⚠️ Warning	This pull request includes updates to uv.lock for pytest installation and adds UI tooltips, neither of which align with the scope of issue #12’s requirement to centralize existing strings into a module, introducing unrelated changes.	Split unrelated dependency updates and UI enhancements into separate pull requests and focus this branch solely on migrating strings to a shared module as specified in issue #12.
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 (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title succinctly describes the two primary changes—adding tooltips and updating the uv.lock file after installing pytest—using clear, specific language without extraneous details.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0055024 and eed19cc.

📒 Files selected for processing (1)

• src/edit_python_pe/main.py (4 hunks)

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

• src/edit_python_pe/main.py

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

src/edit_python_pe/main.py (2)

119-127: Add tooltip for the list-view Quit button for parity.
Form view has a Quit tooltip; list view’s Quit lacks one.

Apply this minimal diff:

 self.quit_list_button = Button(BUTTON_QUIT, id="quit_list")
+self.quit_list_button.tooltip = "Exit the app"

---

58-61: Consider centralizing tooltip strings for consistency/i18n.
Most strings are already centralized in .strings; tooltips could live there too to keep style consistent and ease localization.

I can draft TOOLTIP_* constants in .strings and a patch that replaces these inline literals—want me to open a follow-up PR?

Also applies to: 82-85, 119-119, 124-124, 140-140, 143-143, 146-146, 149-149, 152-152, 155-155, 158-158, 161-161, 166-166, 169-169, 172-172, 175-175, 178-178

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9700307 and 0055024.

📒 Files selected for processing (1)

• src/edit_python_pe/main.py (4 hunks)

🔇 Additional comments (5)

src/edit_python_pe/main.py (5)

58-61: LGTM: SocialEntry tooltips add clarity.
Clear, action-oriented phrasing.

---

82-85: LGTM: AliasEntry tooltips add clarity.
Consistent verbs and tone with other tooltips.

---

140-161: LGTM: Form field tooltips improve usability.
Good coverage across inputs and text areas; phrasing is concise.

---

166-178: LGTM: Action button tooltips are clear and aligned with intent.
Nice consistency across Save, Back, Quit.

---

58-61: .tooltip property assignment is correct for Textual v3.1.0
Project pins textual==3.1.0, and the official API uses the .tooltip property to set tooltips(github.com)

Likely an incorrect or invalid review comment.