feat: add sensitive data tooltips to all form fields

[Zewang0217]

Added tooltip attribute to name_input, email_input, city_input, and homepage_input fields.

Added tooltip attribute to all TextArea fields (who_area, python_area, contributions_area, availability_area).

All tooltips provide clear explanations of how the data will be used and stored.

Summary by CodeRabbit

• New Features
  • Added descriptive tooltips to profile form fields to guide users on what to enter and clarify which details are public versus private.
  • Tooltips now appear for name, email, city, and homepage inputs, plus “About you,” Python involvement, contributions, and availability text areas.
  • Placeholders and form behavior remain unchanged; tooltips improve clarity without affecting workflows.

[coderabbitai]

Walkthrough

Added tooltip text to four Input fields and four TextArea fields within on_mount in src/edit_python_pe/main.py. Placeholders and component order remain unchanged. No control flow, data handling, or public APIs were modified.

Changes

Cohort / File(s)	Summary of edits
UI tooltip additions src/edit_python_pe/main.py	Added tooltip parameters to Input fields (name, email, city, homepage) and TextArea fields (who_area, python_area, contributions_area, availability_area) in on_mount. Placeholders preserved; no logic or behavior changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I nibble notes on fields so neat,
Little hints where users meet—
Tooltips bloom like clover bright,
Guide the paws, left and right.
Forms now whisper what to share,
Privacy clear as autumn air.
Thump-thump! UX done just right.

---

📜 Recent 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 164b957 and 8fb3566.

📒 Files selected for processing (1)

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

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

• src/edit_python_pe/main.py

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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.

CodeRabbit Configuration 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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: 1

🧹 Nitpick comments (1)

src/edit_python_pe/main.py (1)

84-87: Make availability tooltip explicit about public visibility; keep phrasing consistent.

• Other sections clearly indicate public visibility; availability does not. Align it to avoid surprises.

-        self.availability_area = TextArea(tooltip="Your availability information will help community members know when they can reach out.")
+        self.availability_area = TextArea(tooltip="Your availability will be publicly visible to help community members know when they can reach out.")

Optional: consider moving these tooltip strings into .strings for consistency and future i18n.

📜 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 366243f and 164b957.

📒 Files selected for processing (1)

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

[Zewang0217]

@coderabbitai Thanks for the thorough review! I've addressed your comments:

1. Updated the email tooltip to accurately reflect that the email may be publicly visible in the repository outputs.

2. Removed backslash line continuations and used parenthesized string literals for better code style.

3. Adjusted the availability tooltip to explicitly mention public visibility for consistency.

The changes have been pushed. Please take another look when you have a moment.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@Zewang0217 Excellent work! I've reviewed the updated changes and can confirm you've successfully addressed all the feedback points:

✅ Email tooltip accuracy: The tooltip now correctly states the email "may be publicly visible in repository outputs" - much more accurate than the previous wording.

✅ Code style improvement: Great job replacing the backslash line continuations with parenthesized string literals. This follows Python best practices and makes the code more readable.

✅ Consistency in availability tooltip: The availability tooltip now explicitly mentions "publicly visible" which maintains consistency with the other tooltips.

The tooltips are now comprehensive, accurate, and properly formatted. Users will have clear expectations about how their data will be used and displayed. The code style improvements also enhance maintainability.

The implementation looks solid and ready for merge! 🎉

---

🏁 Script executed:

#!/bin/bash
# Get the current content of the main.py file to review the updates
cat src/edit_python_pe/main.py

Length of output: 13814

---

@Zewang0217 I've reviewed the updated code, and while I see some improvements, there are several issues that need to be addressed:

Issues Found:

1. Homepage tooltip bug: The homepage input tooltip currently says:

   "Your availability will be publicly visible to help community members know when they can reach out."
   

   This appears to be a copy-paste error from the availability tooltip. It should describe the homepage field instead.

2. Email tooltip accuracy: The current email tooltip says "may appear in the repository or site outputs" but you mentioned updating it to say "publicly visible in repository outputs" - there's a slight discrepancy.

3. Availability tooltip consistency: The availability tooltip doesn't mention "publicly visible" as you indicated. It currently says:

   "Your availability information will help community members know when they can reach out."
   

What's Working Well:

✅ Code style: Great job using parenthesized string literals instead of backslash continuations - much cleaner!

Recommended Fixes:

# Fix the homepage tooltip
self.homepage_input = Input(placeholder=PLACEHOLDER_HOMEPAGE,
                           tooltip="Your homepage URL will be publicly visible on your profile to help others learn more about your work.")

# Make email tooltip more explicit about public visibility  
self.email_input = Input(placeholder=PLACEHOLDER_EMAIL,
                        tooltip="Your email may be publicly visible in repository outputs. "
                        "Only provide an address you are comfortable sharing publicly.")

# Add "publicly visible" to availability tooltip for consistency
self.availability_area = TextArea(tooltip="Your availability information will be publicly visible to help community members know when they can reach out.")

Could you please fix these tooltip issues, particularly the homepage tooltip bug?

---

If you found this review helpful, would you consider giving us a shout-out on X?

Thank you for using CodeRabbit!