bit-badger/jobs-jobs-jobs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 19 Activity

Add "real name" field #12

New Issue
Closed
opened 2021-02-05 14:11:04 +00:00 by danieljsummers · 2 comments
danieljsummers commented 2021-02-05 14:11:04 +00:00 (Migrated from github.com)
Copy Link

Add a field where users can put in their real names, which will be displayed at the top of the employment profile. In general, and throughout the application, where we currently use the display name, use the real name (if entered), defaulting to display name. Continue to update the display name on each login as we currently do.

Add a field where users can put in their real names, which will be displayed at the top of the employment profile. In general, and throughout the application, where we currently use the display name, use the real name (if entered), defaulting to display name. Continue to update the display name on each login as we currently do.
danieljsummers commented 2021-02-07 00:19:22 +00:00 (Migrated from github.com)
Copy Link

This will be a part of the initial release. To provide the real name field:

  • Add a real_name column / RealName property for the citizen
  • Add an optional field for the real name to the profile edit page

Once this is done, following are the changes that should be applied to display names:

  • Modify the display_name column / DisplayName to be nullable
  • Undo the change for #11 that puts the handle in the display name column if it's blank; instead, insert null if it's blank
  • Create a CitizenName property that displays the first non-null value from (in order) RealName, DisplayName, and NaUser
  • Modify all areas in the application where DisplayName is being used to use CitizenName instead

Finally, run a query to set display_name to null if its value matches the na_user column.

This will be a part of the initial release. To provide the real name field: - Add a `real_name` column / `RealName` property for the citizen - Add an optional field for the real name to the profile edit page Once this is done, following are the changes that should be applied to display names: - Modify the `display_name` column / `DisplayName` to be nullable - Undo the change for #11 that puts the handle in the display name column if it's blank; instead, insert `null` if it's blank - Create a `CitizenName` property that displays the first non-null value from (in order) `RealName`, `DisplayName`, and `NaUser` - Modify all areas in the application where `DisplayName` is being used to use `CitizenName` instead Finally, run a query to set `display_name` to `null` if its value matches the `na_user` column.
danieljsummers commented 2021-02-07 22:10:35 +00:00 (Migrated from github.com)
Copy Link

This is done, ready for v1.0

This is done, ready for v1.0
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
infrastructure
Keep the application up and current
invalid
This doesn't seem right
question
Further information is requested
wontfix
This will not be worked on
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
danieljsummers
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bit-badger/jobs-jobs-jobs#12
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?