In some parts of the app, the user's internal ID is displayed instead of their display name/username.
Steps to reproduce
Browse views that show user information (e.g. track uploader, profiles, followers/following, playlist owner, search results).
Observe that in some places an ID is shown instead of the name.
Expected behavior
The user's display name (or username as fallback) is shown everywhere a user is referenced. IDs should never be shown in the UI.
Actual behavior
The raw user ID is displayed.
Suggested fix
Check that the API returns the user's name in the affected responses (populate/join the user data instead of returning only the ID).
Use a shared component/helper to render user names so the fallback logic is consistent.
## Description
In some parts of the app, the user's internal ID is displayed instead of their display name/username.
## Steps to reproduce
1. Browse views that show user information (e.g. track uploader, profiles, followers/following, playlist owner, search results).
2. Observe that in some places an ID is shown instead of the name.
## Expected behavior
The user's display name (or username as fallback) is shown everywhere a user is referenced. IDs should never be shown in the UI.
## Actual behavior
The raw user ID is displayed.
## Suggested fix
- Check that the API returns the user's name in the affected responses (populate/join the user data instead of returning only the ID).
- Use a shared component/helper to render user names so the fallback logic is consistent.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
In some parts of the app, the user's internal ID is displayed instead of their display name/username.
Steps to reproduce
Expected behavior
The user's display name (or username as fallback) is shown everywhere a user is referenced. IDs should never be shown in the UI.
Actual behavior
The raw user ID is displayed.
Suggested fix