Improve user name handling
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- full-stack, web-dev
Research direction
Start by locating the user model, the profile page, and the migration handling first_name and last_name. Review how names are displayed and edited; done means existing names are migrated, users can update a single name from their profile, and the behavior is covered by tests.
Written by the indexing model from the issue text.
Description
Currently, Patchwork user accounts have immutable first_name and last_name fields. This can result in a number of issues (see Falsehoods Programmers Believe About Names for a more extensive list), but most significantly results in the following:
- Users who go by a mononym (not uncommon in pseudonymous software developers)
- Users cannot update their account if their name changes (not uncommon in general)
I'd suggest making the following changes:
- Switch to a single "name" field. The two separate name fields seem to always simply be concatenated with a space for display, so this can be handled for existing users by simply doing the same in a migration. This may not be the best solution for some users (e.g. eastern name order, more than 2 names, etc…), but it'll be no worse than the current behavior, and they'll be able to fix it.
- Provide an option to change their name from their profile page. As far as I can tell, the display name isn't used for any security-relevant purpose, so I don't believe this should cause any problems.
- Dominant language
- Python
- Stars
- 317
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getpatchwork/patchwork
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
getpatchwork/patchwork#546 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
getpatchwork/patchwork#664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
getpatchwork/patchwork#663 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
getpatchwork/patchwork#645 ·
All issues in getpatchwork/patchwork
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·