Prioritizing full name vs username in the UX

[sam (Sam Saffron)]

I just added a site setting that allows you to prioritize full names as opposed to usernames in the UI.

When usernames are prioritized cause the site setting prioritize_username_in_ux is enabled you will see:

In card:

On user page:

In post stream:

If you change it so prioritize_username_in_ux is disabled you will see:

In card:

On user page:

In post stream:

I feel an @ symbol may be worth adding per:

This can be done safely via CSS, leaving it off for now.

Quotes inside the UX still pull in username eg:

@sam

Eg: this quote is going to sam: as opposed to sam saffron:

We may look at making this switch to be fullname based when the setting is set.

[riking (Kane York)]

Bug report: If full name is blankish, username is offset and not fully bold

[mcwumbly (Dave McClure)]

eh?

Full name @mentions

It would look more elegent in posts if @leo (for example) was presented as (or at least the user had the option to present it as) “Leo” or “Leo McArdle”.

[sam (Sam Saffron)]

corrected per

https://github.com/discourse/discourse/commit/0e2d918b3b3807041126bc66d3e0d205d42c7820

Still abusable, but we might as well correct that server side by doing a trim on save that is unicode aware.

[sam (Sam Saffron)]

That is a can-of-worms to implement, same class as improving quotes. I may get to it, but not for this round.

[gerhard (Gerhard Schlager)]

@sam

I feel an @ symbol may be worth adding per:

https://d11a6trkgmumsb.cloudfront.net/original/3X/d/0/d0c5b1049a0693259beec3cd229052dff5e07abd.png

I believe the username should be shown with @ by the default. It’s a lot less confusing.

And the username should always be visible. Don’t make me think.

[codinghorror (Jeff Atwood)]

At symbol too noisy repeated all over the page. In the user card should suffice.

[jerry0 (Jerry)]

Esto funciona en casi todos los lugares, pero no en las notificaciones por correo electrónico.

Por ejemplo, en la tarjeta de usuario se ve bien.

Pero en las notificaciones por correo electrónico, el nombre completo no tiene prioridad:

(También creo que solo uno de los dos nombres necesita estar hipervinculado, el primero, supongo).

[sam (Sam Saffron)]

@techAPJ ¿puedes investigar una solución para los correos electrónicos?

[techAPJ (Arpit Jalan)]

Corregido mediante:

FIX: respect prioritize_username_in_ux setting in email

Cuando prioritize_username_in_ux está habilitado:

Cuando prioritize_username_in_ux está deshabilitado:

[techAPJ (Arpit Jalan)]

Se simplificó aún más el estilo para usar el mismo CSS para username y user-name. (Observa el grosor de fuente en negrita para username frente al normal para user-name.)

UX: use same styling for username and user-name

[techAPJ (Arpit Jalan)]

He aplicado otra corrección aquí para la página /about:

FIX: respect `prioritize_username_in_ux` setting on /about page

[mentalstring (Paulo)]

He encontrado un lugar donde esta configuración no parece estar surtiendo efecto: la lista de coincidencias de nombres de usuario en los resultados de búsqueda:

Geminiscp es el nombre de usuario y prioritize username in ux = true.

[debryc (Deborah Chang)]

Acabamos de instalar la barra lateral y el chat experimentales. ¿Se pueden priorizar también los nombres completos en la sección de chat personal si deshabilitamos prioritize_username_in_ux?