Merged
Conversation
✅ Deploy Preview for partners-bloom-msq2 canceled.
|
✅ Deploy Preview for bloom-angelopolis ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
a43e2ed to
57964e5
Compare
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
emilyjablonski
commented
Feb 25, 2026
ludtkemorgan
approved these changes
Feb 26, 2026
Collaborator
ludtkemorgan
left a comment
There was a problem hiding this comment.
Change looks great!!
5022f92 to
729ec46
Compare
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses #5944
Description
This ticket assumes an advocate is already created and approved. It covers editing the account information in the user's dashboard when logged in. The work to use to same form fields to actually create the account will be a different PR.
How Can This Be Tested/Reviewed?
I separated out the sections into helper functions to reduce duplication between the public user edit account and advocate user edit account pages. We can plug any of the individual sections into account forms. We will also be able to use them for the upcoming advocate request form, and could use them on the public create form as well.
I think the per-field update button pattern we have is weird, but a redesign of this existing pattern is out of scope for these tickets.
We should test the public user edit account page and the advocate user edit account page. We should be able to update each section.
Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: