araemer/recipe-platform
1
0
Fork 0
Code Issues 13 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Feature request: nickname and choice of displayed name #21

New issue
Open
opened 2026-09-27 18:20:50 +00:00 by araemer · 0 comments
araemer commented 2026-09-27 18:20:50 +00:00
Owner
Copy link

Idea

Today, users are shown by their real name (first and last name) everywhere other users can see them: comments, ratings, meal plan sharing, and soon shopping list sharing. With spec 001, a user directory endpoint makes every user's name visible to every other user when picking someone to share with.

Introduce an optional nickname per user, plus a setting in the user profile to choose how they appear to others:

  • real name
  • nickname

All places that display another user (comments, ratings, share dialogs, shopping list "added by", "shared by") then use the chosen display name.

Notes

  • Affects the user model, the user settings UI, and every DTO that exposes another user's name. Spec 001 introduces a reduced UserSummaryDto for that purpose, which would be the natural place for a resolved display name.
  • Needs a PO discussion and its own spec.

Raised during the cross-cutting architecture discussion of spec 001.

## Idea Today, users are shown by their real name (first and last name) everywhere other users can see them: comments, ratings, meal plan sharing, and soon shopping list sharing. With spec 001, a user directory endpoint makes every user's name visible to every other user when picking someone to share with. Introduce an optional **nickname** per user, plus a setting in the user profile to choose how they appear to others: - real name - nickname All places that display another user (comments, ratings, share dialogs, shopping list "added by", "shared by") then use the chosen display name. ## Notes - Affects the user model, the user settings UI, and every DTO that exposes another user's name. Spec 001 introduces a reduced `UserSummaryDto` for that purpose, which would be the natural place for a resolved display name. - Needs a PO discussion and its own spec. Raised during the cross-cutting architecture discussion of spec 001.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
004-fill-list-from-meal-plan-status
004-fill-list-from-meal-plan-gate-b
004-fill-list-from-meal-plan-contract
004-fill-list-from-meal-plan
team-definition
release-pr-gate
003-compact-user-in-embedded-dtos-contract
003-compact-user-in-embedded-dtos-status
003-compact-user-in-embedded-dtos
002-shopping-list-overview-previews-status
002-shopping-list-overview-previews-card-layout
contract-pin
002-shopping-list-overview-previews
plan-feature-branches
001-shopping-lists
epic-layer
release-script
workflow-review-fixes
shared-workflow-plugin
build-contract-for-node
add-pr-feedback-skill
fix-image-route-path-pattern
fix-contract-mandatory-fields
add-consent-rule
sibling-repo-work-via-subagent
fix-contract-ci-install-step
fix-contract-ci-clone-mechanism
fix-recipes-contract-unused-import
fix-skill-format
bootstrap-orchestration-repo
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
araemer/recipe-platform#21
No description provided.