feat(2447): implement profile edit (visibility, acc. details, email prefs)#2517
feat(2447): implement profile edit (visibility, acc. details, email prefs)#2517ycanales wants to merge 7 commits into
Conversation
|
Warning Review limit reached
Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
📝 WalkthroughWalkthroughAdds country and profile-visibility fields, extends V3 form validation and email choices, restructures profile editing into independent section forms, adds section-specific request handling, updates field and card styling, and introduces comprehensive tests. ChangesV3 profile edit multi-section update
Estimated code review effort: 4 (Complex) | ~60 minutes Sequence Diagram(s)sequenceDiagram
participant Browser
participant CurrentUserProfileView
participant V3UserProfileForm
participant User
Browser->>CurrentUserProfileView: POST profile-account?edit=true with section button
CurrentUserProfileView->>CurrentUserProfileView: dispatch() checks authentication
CurrentUserProfileView->>CurrentUserProfileView: post_v3() selects submitted section
CurrentUserProfileView->>V3UserProfileForm: Validate section-owned fields
V3UserProfileForm-->>CurrentUserProfileView: Validation result
CurrentUserProfileView->>User: Save selected section when valid
CurrentUserProfileView-->>Browser: Return JSON or redirect
Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (2)
users/tests/test_v3_profile_edit.py (1)
68-84: 🎯 Functional Correctness | 🔵 Trivial | 💤 Low valueAdd a True→False transition case for a hide toggle.
This test only exercises turning toggles on from their default (
False) state;hide_badges is Falseis asserted but never actually toggled off from a pre-existingTrue. Consider seedinguser.hide_badges = Truebefore the POST (withhide_achomitted) to confirm the section correctly unsets it.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@users/tests/test_v3_profile_edit.py` around lines 68 - 84, The v3 profile edit test only covers toggles being turned on from their default state, so it misses the True-to-False path for a hide toggle. Update the test in test_v3_update_profile_saves_visibility_toggles by seeding the user’s hide_badges to True before the POST, then omit the corresponding toggle field in the form data so the profile update flow can be verified to clear it. Keep the existing assertions on user.refresh_from_db() and add/adjust the final assertion to confirm hide_badges is unset after the update.users/views.py (1)
536-557: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueMutable class attribute flagged by Ruff (RUF012).
V3_EDIT_SECTIONSis a plain dict assigned as a class attribute; Ruff's RUF012 recommends annotating it astyping.ClassVar[dict[...]](or using a different construct) to make the shared, immutable-in-practice nature explicit and silence the linter.♻️ Suggested annotation
+from typing import ClassVar + - V3_EDIT_SECTIONS = { + V3_EDIT_SECTIONS: ClassVar[dict] = {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@users/views.py` around lines 536 - 557, V3_EDIT_SECTIONS is a mutable class-level dict and Ruff flags it under RUF012; update the declaration to make its shared, read-only intent explicit by annotating it with typing.ClassVar (or moving it to an immutable construct). Keep the fix centered on the V3_EDIT_SECTIONS constant in the view class so the linter recognizes it as a class attribute rather than an instance field.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@templates/v3/user_profile_edit.html`:
- Line 180: The Country field in the user profile edit template is passing a
separate placeholder even though country_options already contains the empty
“Select” option, causing duplicate “Select” entries in the no-JS select. Update
the include for _field_combo.html in user_profile_edit.html to rely on
country_options alone and remove the placeholder argument, keeping the
selected/error wiring unchanged.
In `@users/forms.py`:
- Around line 255-265: The `clean_username` check in `users.forms` only
validates uniqueness at the form layer, so concurrent writes can still create
duplicate `User.display_name` values. Add a database-backed case-insensitive
uniqueness guarantee on `users.User` using a `UniqueConstraint` with
`Lower("display_name")`, and include the necessary migration/data cleanup to
resolve any existing duplicates before applying it. Also update the save path
for `User` so `IntegrityError` from the database is caught and surfaced as the
same “already taken” validation error, keeping the enforcement consistent in
both `clean_username` and the model save flow.
In `@users/tests/test_v3_profile_edit.py`:
- Around line 86-105: Add coverage for the omitted-checkbox path in the v3
profile edit tests: the current test for v3_update_details only checks the
checked state, but _save_v3_details_section reads booleans directly from
form.cleaned_data so absent checkbox keys should reset to False. Add a test
around test_v3_update_details_saves_account_fields (or a sibling test) that
starts with is_commit_author_name_overridden and indicate_last_login_method
already True, submits the profile-account form via tp.post without those two
keys, and asserts both fields become False after refresh_from_db.
---
Nitpick comments:
In `@users/tests/test_v3_profile_edit.py`:
- Around line 68-84: The v3 profile edit test only covers toggles being turned
on from their default state, so it misses the True-to-False path for a hide
toggle. Update the test in test_v3_update_profile_saves_visibility_toggles by
seeding the user’s hide_badges to True before the POST, then omit the
corresponding toggle field in the form data so the profile update flow can be
verified to clear it. Keep the existing assertions on user.refresh_from_db() and
add/adjust the final assertion to confirm hide_badges is unset after the update.
In `@users/views.py`:
- Around line 536-557: V3_EDIT_SECTIONS is a mutable class-level dict and Ruff
flags it under RUF012; update the declaration to make its shared, read-only
intent explicit by annotating it with typing.ClassVar (or moving it to an
immutable construct). Keep the fix centered on the V3_EDIT_SECTIONS constant in
the view class so the linter recognizes it as a class attribute rather than an
instance field.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 1dce707a-6b90-405a-a972-3619c7aeeb50
📒 Files selected for processing (10)
static/css/v3/card.csstemplates/v3/includes/_button.htmltemplates/v3/includes/_field_include.htmltemplates/v3/includes/_field_text.htmltemplates/v3/user_profile_edit.htmlusers/forms.pyusers/migrations/0022_user_country_user_hide_badges_and_more.pyusers/models.pyusers/tests/test_v3_profile_edit.pyusers/views.py
| {% include 'v3/includes/_field_include.html' with bound_field=user_profile_form.username %} | ||
| {% include 'v3/includes/_field_include.html' with bound_field=user_profile_form.email %} | ||
| {% include 'v3/includes/_field_include.html' with bound_field=user_profile_form.country %} | ||
| {% include 'v3/includes/_field_combo.html' with name=user_profile_form.country.name label='Country' options=country_options selected=user_profile_form.country.value placeholder='Select' error=user_profile_form.country.errors.0 %} |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
fd _field_combo.html
cat templates/v3/includes/_field_combo.html 2>/dev/nullRepository: boostorg/website-v2
Length of output: 7378
Avoid passing a separate placeholder here
country_options already includes ("", "Select"), so placeholder='Select' makes the no-JS <select> render two identical “Select” entries. Drop one of them.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@templates/v3/user_profile_edit.html` at line 180, The Country field in the
user profile edit template is passing a separate placeholder even though
country_options already contains the empty “Select” option, causing duplicate
“Select” entries in the no-JS select. Update the include for _field_combo.html
in user_profile_edit.html to rely on country_options alone and remove the
placeholder argument, keeping the selected/error wiring unchanged.
| def clean_username(self): | ||
| username = self.cleaned_data["username"] | ||
| if not username: | ||
| return username | ||
| existing = User.objects.filter(display_name__iexact=username) | ||
| if self._user is not None: | ||
| existing = existing.exclude(pk=self._user.pk) | ||
| if existing.exists(): | ||
| raise forms.ValidationError("This username is already taken") | ||
| return username | ||
|
|
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== files ==\n'
git ls-files users/forms.py users/models.py users/migrations || true
printf '\n== users/forms.py (around clean_username) ==\n'
nl -ba users/forms.py | sed -n '230,290p'
printf '\n== users/models.py (relevant parts) ==\n'
nl -ba users/models.py | sed -n '1,260p'
printf '\n== search for display_name constraints / uniqueness / integrity handling ==\n'
rg -n "display_name|UniqueConstraint|unique=True|IntegrityError|Lower\(" users -g '!**/__pycache__/**'
printf '\n== migrations mentioning display_name ==\n'
rg -n "display_name|UniqueConstraint|unique=True|Lower\(" users/migrations -g '!**/__pycache__/**'Repository: boostorg/website-v2
Length of output: 1353
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== users/forms.py (around clean_username) ==\n'
sed -n '240,285p' users/forms.py | cat -n
printf '\n== users/models.py (top + User model area) ==\n'
sed -n '1,260p' users/models.py | cat -n
printf '\n== users/migrations/0009_user_display_name.py ==\n'
sed -n '1,220p' users/migrations/0009_user_display_name.py | cat -n
printf '\n== users/migrations/0017_populate_users_display_name.py ==\n'
sed -n '1,220p' users/migrations/0017_populate_users_display_name.py | cat -n
printf '\n== search for IntegrityError / unique constraints / display_name ==\n'
grep -RIn --exclude-dir='__pycache__' -E 'display_name|UniqueConstraint|unique=True|IntegrityError|Lower\(' users | head -n 200Repository: boostorg/website-v2
Length of output: 19906
users/forms.py:255-265 — Add a DB-level uniqueness constraint for User.display_name
clean_username() only enforces this in the form, so concurrent saves can still create duplicate display names. Add a case-insensitive UniqueConstraint(Lower("display_name")) on users.User with a migration/data cleanup for existing duplicates, and handle IntegrityError on save so the “already taken” error is enforced by the database too.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@users/forms.py` around lines 255 - 265, The `clean_username` check in
`users.forms` only validates uniqueness at the form layer, so concurrent writes
can still create duplicate `User.display_name` values. Add a database-backed
case-insensitive uniqueness guarantee on `users.User` using a `UniqueConstraint`
with `Lower("display_name")`, and include the necessary migration/data cleanup
to resolve any existing duplicates before applying it. Also update the save path
for `User` so `IntegrityError` from the database is caught and surfaced as the
same “already taken” validation error, keeping the enforcement consistent in
both `clean_username` and the model save flow.
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
gh pr view 2521 --repo boostorg/website-v2 --json title,body,state,urlLength of output: 484
@julhoang, I tried to look up #2521 for context but couldn't resolve it (GitHub CLI returned "Could not resolve to a PullRequest with the number of 2521"), so it may not exist yet, or the sandbox doesn't have visibility into it. I'll leave it to @ycanales to confirm whether that PR covers the DB-level uniqueness constraint for display_name. Happy to take another look once it's available or if there's more context to share.
…sibility # Conflicts: # users/forms.py # users/views.py
|
On removing the In the Update Details card, the field sits in an unbroken chain of definite-height containers: the grid stretches .user-profile__col to the row height, and from there card → Tagline and the other inputs never broke because they sit inside plain block divs, which make the parent height indefinite; there height: 100% silently fell back to auto. Before: After: I double-checked other views to confirm heights were not affected:
|
julhoang
left a comment
julhoang
left a comment
There was a problem hiding this comment.
Hi @ycanales ! This is great work! I just ran into 1 issue with saving the Override commit author email UI field. Would you mind double-checking this?
User.Profile.Field.not.saved.1.mp4
Also, per the Figma design, the button text should be updated to Changes saved instead of announcing via the toast message. Can we suppress the legacy toast message on this page?
| <div class="card__cta_section"> | ||
| {% include 'v3/includes/_button.html' with style='primary' type='submit' label='Save Changes' only %} | ||
| {% include 'v3/includes/_button.html' with style='primary' type='submit' name='v3_update_profile' label='Save changes' only %} | ||
| {% include 'v3/includes/_button.html' with style='secondary' url=profile_account_url label='Cancel' only %} |
There was a problem hiding this comment.
Instead of redirecting user back to "My Profile", I think it'd make a greater UX if we allow users to remain on the Edit User page with just the temporary form data revert. To do that, I think we just need to replace url=profile_account_url with type='reset' here.
There was a problem hiding this comment.
Good catch on the toast/"Changes Saves" button, here it is:
If you change again a value, the button changes back:
I addressed the "Cancel" behavior too, I wonder though, maybe the Figma is missing the "Cancel" in the other sections too, or could it be intentional?
herzog0
left a comment
herzog0
left a comment
There was a problem hiding this comment.
Looking good, just one nit, one requirement and one note: about the "Override commit author email address" feature, don't worry about that (cc @julhoang) as this will be addressed in a dedicated ticket. This feature shouldn't be implemented as this design reference states anyway.
| {% comment %} novalidate: this form still contains required fields (tagline, bio, links) with | ||
| no save handler yet; native constraint validation would silently block "Save changes" for | ||
| sections that are otherwise ready. Server-side validation is authoritative. {% endcomment %} | ||
| <form method="post" action="{% url 'profile-account' %}?edit=true" class="card__form" enctype="multipart/form-data" novalidate> |
There was a problem hiding this comment.
Nit: Can we build the edit URL in the backend an hydrate it in the view, please?
There was a problem hiding this comment.
Addressed, thanks!
| {% include 'v3/includes/_field_include.html' with bound_field=user_profile_form.username %} | ||
| {% include 'v3/includes/_field_include.html' with bound_field=user_profile_form.email %} | ||
| {% include 'v3/includes/_field_include.html' with bound_field=user_profile_form.country %} | ||
| {% include 'v3/includes/_field_combo.html' with name=user_profile_form.country.name label='Country' options=country_options selected=user_profile_form.country.value placeholder='Select' error=user_profile_form.country.errors.0 %} |
There was a problem hiding this comment.
Per the ticket, the user should also be able to select a blank/no country option to hide their flag if they don't wanna disclose that info anymore. Currently, there's no way to do that.
There was a problem hiding this comment.
Good catch! Now when the user selects "No country" the select clears and is persisted when saving the form. Thanks Teo 👍
There was a problem hiding this comment.
We actually do have a deselectable version of some dropdowns which were used on the Libraries page (I think I only added it to _field_combo_multi.html and _field_dropdown.html), I'm curious if we can use the same design here 🤔 That being said, I think the "None" option works great too!
cc @henryajisegiri
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
users/tests/test_v3_profile_edit.py (1)
147-164: 🗄️ Data Integrity & Integration | 🔴 Critical | 🏗️ Heavy liftNon-submitted form sections are visually erased on validation failure.
Because the V3 page uses independent HTML
<form>elements, submitting this section meansrequest.POSTonly contains the details fields. However, when the backend encounters a validation error, it binds the entireV3UserProfileFormto that partialrequest.POST.In Django, binding a form with missing fields causes those fields to evaluate to their empty defaults (e.g., empty strings for text fields,
Falsefor checkboxes), completely ignoring theinitialdata. Consequently, when the server returns a200 OKHTML page to display the validation error, the user will see the fields in their other sections wiped out.Please add an assertion to verify that cross-section fields (like
taglineorhide_github) retain their initial values when validation fails, and implement a fix in the backend to populate missing fields before binding.🐛 Proposed test enhancement
with tp.login(user): response = tp.post( f"{tp.reverse('profile-account')}?edit=true", data={ "v3_update_details": "true", "username": "taken", "country": "US", }, ) assert response.status_code == 200 assert "A user with that username already exists." in response.content.decode() + + # Ensure fields from other sections didn't get wiped out in the rendered HTML + html = response.content.decode() + assert user.tagline in html, "Fields from other sections were erased from the HTML response!" # user not changedTo fix the backend logic, you can merge the
initialdata into a mutable copy ofrequest.POSTinsidepost_v3before passing it toV3UserProfileForm:# Ensure non-submitted fields don't render as empty/unchecked on validation failure post_data = request.POST.copy() for name, value in self.get_v3_edit_initial().items(): if name not in section_fields and name not in post_data: # Add it as a string so bound_data can process it correctly if isinstance(value, bool): if value: post_data[name] = "on" elif value is not None: post_data[name] = str(value) form = V3UserProfileForm( post_data, # ... )🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@users/tests/test_v3_profile_edit.py` around lines 147 - 164, Update the V3 validation flow in post_v3 so partial section submissions merge missing fields from get_v3_edit_initial() into a mutable copy of request.POST before constructing V3UserProfileForm; preserve submitted values, encode truthy booleans as checked values, and omit false or null values. Extend test_v3_update_details_duplicate_username_shows_inline_error to assert cross-section fields such as tagline or hide_github retain their initial values after the validation failure.
🧹 Nitpick comments (2)
users/forms.py (1)
233-235: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winResolve Ruff RUF005.
Prefer the unpacking form to satisfy the configured lint rule without changing behavior:
- self.fields["country"].choices = [("", "No country")] + list(countries) + self.fields["country"].choices = [("", "No country"), *list(countries)]🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@users/forms.py` around lines 233 - 235, Update the country choices assignment in the form initializer to use iterable unpacking instead of list concatenation, preserving the existing “No country” option followed by all countries and satisfying Ruff RUF005.Source: Linters/SAST tools
templates/v3/user_profile_edit.html (1)
305-342: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueConsider registering the Alpine component via
Alpine.data.While assigning the initialization function to the global
windowobject works perfectly, registering it viaAlpine.dataavoids polluting the global scope and aligns more closely with Alpine.js best practices for reusable components.🛠️ Proposed refactor
- window.createSectionForm = function (initialSaved) { - return { + document.addEventListener('alpine:init', () => { + Alpine.data('sectionForm', (initialSaved) => ({ saved: initialSaved, _bypassFetch: false, async handleSubmit(event) { // ... }, - } - } + })) + })Then, you can update the HTML forms to use
x-data="sectionForm(...)"instead ofx-data="createSectionForm(...)".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@templates/v3/user_profile_edit.html` around lines 305 - 342, Register the section form component through Alpine.data using the existing createSectionForm initialization logic instead of assigning it to window. Update all corresponding form bindings from x-data="createSectionForm(...)" to x-data="sectionForm(...)", preserving the current submit, success, and fallback behavior.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@users/tests/test_v3_profile_edit.py`:
- Around line 147-164: Update the V3 validation flow in post_v3 so partial
section submissions merge missing fields from get_v3_edit_initial() into a
mutable copy of request.POST before constructing V3UserProfileForm; preserve
submitted values, encode truthy booleans as checked values, and omit false or
null values. Extend test_v3_update_details_duplicate_username_shows_inline_error
to assert cross-section fields such as tagline or hide_github retain their
initial values after the validation failure.
---
Nitpick comments:
In `@templates/v3/user_profile_edit.html`:
- Around line 305-342: Register the section form component through Alpine.data
using the existing createSectionForm initialization logic instead of assigning
it to window. Update all corresponding form bindings from
x-data="createSectionForm(...)" to x-data="sectionForm(...)", preserving the
current submit, success, and fallback behavior.
In `@users/forms.py`:
- Around line 233-235: Update the country choices assignment in the form
initializer to use iterable unpacking instead of list concatenation, preserving
the existing “No country” option followed by all countries and satisfying Ruff
RUF005.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 18eb471d-acb1-4b00-a826-132a4e241f4d
📒 Files selected for processing (5)
templates/v3/includes/_button.htmltemplates/v3/user_profile_edit.htmlusers/forms.pyusers/tests/test_v3_profile_edit.pyusers/views.py
🚧 Files skipped from review as they are similar to previous changes (2)
- templates/v3/includes/_button.html
- users/views.py
…sibility # Conflicts: # templates/v3/includes/_button.html # templates/v3/user_profile_edit.html # users/models.py # users/views.py
|
Merged develop into my branch and solved conflicts while keeping changes from both sides. |
|
Addressed CodeRabbit suggestion on non-submitted form sections being visually erased on validation failure. |
julhoang
left a comment
julhoang
left a comment
There was a problem hiding this comment.
Woops we're now having an extra Save button in this section 😆, would you mind double-checking this?
3 participants
Issue: #2447
Summary & Context
Wires the v3 edit-profile page (shell landed in Story 2437) so three of its cards actually validate and persist: profile visibility toggles, account details (username, country), and email preferences. Adds four new
Userfields plus a per-section form pattern so each card saves independently.Changes
<form>with a distinct named submit button (v3_update_profile,v3_update_details,v3_update_email_preferences);post_v3()dispatches on the button name and validates/saves only that section, so an unfinished card never blocks a completed one. Section wiring lives in theV3_EDIT_SECTIONSmap inusers/views.py.dispatch()override onCurrentUserProfileViewto enforce login and route v3 POSTs intopost()/post_v3()(the v3 mixin otherwise renders on every request and never reachespost), plusget_v3_edit_initial()/get_v3_edit_context()to seed the form from the current user.Usermodel (migration0022):country(django-countriesCountryField),hide_github_activity,hide_mailing_list_activity, andhide_badges(allBooleanField).User.display_name, with case-insensitive uniqueness inclean_username) and Country (User.country), plus the existingindicate_last_login_methodandis_commit_author_name_overriddentoggles. Country was previously an empty plain dropdown and is now wired to the existing searchable combo (_field_combo.html) populated from django-countries.hide_github/hide_ml/hide_ach).Preferences.notifications(JSONField) via the existing property accessors, using a 4-item choice list (V3_EMAIL_PREFERENCE_CHOICES, no Poll to match Figma); unlisted news types a user already had enabled (e.g. Poll) are preserved on save._button.htmlaccepts aname=so multiple submit buttons can coexist on one page,_field_text.html/_field_include.htmlsurface server-side errors and seed values on re-render, andcard.cssadds.card__formso a<form>can wrap part of a card without breaking its flex-column layout.users/tests/test_v3_profile_edit.py(11 tests) covering login-required GET/POST, current-value rendering, each section's save, blank-country clearing, duplicate-username inline error, email-prefs save, and the Poll-preservation edge case.Please list any potential risks or areas that need extra attention during review/testing
0022adds four columns to theUsertable; needs to run on deploy.email, the Commit email address card, Account connections, and the top of the Profile card (tagline, bio, links, avatar) are still UI-only scaffolding and do not persist yet. Theoverride_commit_author_emailtoggle also has no backing field. These are intentionally out of scope for this PR.Known visual bug: the Username/Email inputs in Update Details render around 22px tall instead of the 40px in Figma (theFixed..field__controlheight is being overridden somewhere), so they look pill-shaped. Still being diagnosed.v3waffle flag.Screenshots
Self-review Checklist
Frontend
Summary by CodeRabbit
Summary by CodeRabbit
New Features
Bug Fixes
Chores