The session user data currently does not include the user’s display name. Exposing this information on the session object would be beneficial, as Discord usernames are not always intended to be user-facing.
I suggest renaming the existing name field to username, and adding a new displayName field populated from userData.global_name.
Additionally, it would be useful to expose more optional profile metadata for UI customization and styling purposes. For example:
bannerbanner_coloraccent_color
These fields would enable developers to more effectively theme user-facing components (such as profiles, headers, and cards) in a manner that aligns with the user’s Discord identity/profile.
There are also a few other pieces of user data that could be valuable, though they are less critical:
- Clan tag
- Clan badge
- Locale
Including these fields would provide a more complete representation of the user and reduce the need for additional API calls in common use cases, while still allowing consumers to opt into using only what they need.
The session user data currently does not include the user’s display name. Exposing this information on the session object would be beneficial, as Discord usernames are not always intended to be user-facing.
I suggest renaming the existing
namefield tousername, and adding a newdisplayNamefield populated fromuserData.global_name.Additionally, it would be useful to expose more optional profile metadata for UI customization and styling purposes. For example:
bannerbanner_coloraccent_colorThese fields would enable developers to more effectively theme user-facing components (such as profiles, headers, and cards) in a manner that aligns with the user’s Discord identity/profile.
There are also a few other pieces of user data that could be valuable, though they are less critical:
Including these fields would provide a more complete representation of the user and reduce the need for additional API calls in common use cases, while still allowing consumers to opt into using only what they need.