added "how did you hear about us" to the signup

[sayanoops]

fixes #219

Summary by CodeRabbit

• New Features
  • Added an optional "How did you hear about us?" field to the sign-up process with descriptive guidance for users.
  • Enhanced the registration experience by allowing users to provide additional feedback during sign-up.
  • Improved data capture to enrich user profiles.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces a new field, "how_did_you_hear_about_us", across several layers of the application. In the admin interface, the field is added to display and edit profiles. The registration form now includes an optional input for users to provide how they discovered the service, with proper widget initialization and saving logic. Corresponding changes are made to the data model and its migration, and the signup HTML template is updated to render the new field.

Changes

File(s)	Summary
web/admin.py	Added the "how_did_you_hear_about_us" field to both ProfileInline and ProfileAdmin classes.
web/forms.py	Introduced a new optional CharField named how_did_you_hear_about_us in UserRegistrationForm with custom widget, initialization logic, and save integration.
web/migrations/0037_profile_how_did_you_hear_about_us.py web/models.py	Added the "how_did_you_hear_about_us" field as a TextField (allowing blank entries with help text) to the Profile model and its corresponding migration.
web/templates/account/signup.html	Updated the signup template to include a textarea for "how_did_you_hear_about_us" with label, placeholder, error handling, and help text.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant T as Signup Template
    participant F as UserRegistrationForm
    participant DB as Profile Model (Database)

    U->>T: Fill out signup form including "How did you hear about us?"
    T->>F: Submit form data
    F->>F: Initialize and validate input (including new field)
    F->>DB: Save profile with "how_did_you_hear_about_us" field
    DB-->>F: Confirmation of save
    F-->>T: Return success response
    T-->>U: Display account creation success message

Loading

Possibly related issues

• add a how did you hear about us to the signup - let the user enter a link or text in one field #219: This PR directly addresses the issue’s request by adding a field to capture how users discovered the service during signup.

---

📜 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 e1f033c and 5527660.

📒 Files selected for processing (5)

• web/admin.py (2 hunks)
• web/forms.py (3 hunks)
• web/migrations/0037_profile_how_did_you_hear_about_us.py (1 hunks)
• web/models.py (1 hunks)
• web/templates/account/signup.html (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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 generate docstrings to generate docstrings for this 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.

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

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]

🚨 Missing Issue Link

This pull request appears to not reference any GitHub issue.

As per our workflow requirements, all PRs should address an existing issue. This ensures:

• Changes are properly tracked
• Work is discussed before implementation
• Code reviews are more focused

How to Fix This

Please link this PR to an existing issue using one of these methods:

1. Reference the issue in your PR description: "Fixes darkmode/about #123" or "Addresses darkmode/about #123"
2. Use GitHub's interface to link the PR to an issue in the Development section
   • Look for the section that says "Development" on the right side of your PR
   • Click "Link an issue" or "Link issues"
   • Select the relevant issue(s)
3. If no issue exists yet, please create one first

This PR will be automatically closed. Feel free to reopen it once you've linked it to an issue or added appropriate labels.

Thank you for your contribution!