Proposal: optional single name field

[fernandoacorreia]

A lot of the codebase is hardwired for the common English name structure of "first name" and "last name". See example 1, example 2.

This anglocentrism is not a good cultural fit for localized applications. For reference, see Falsehoods Programmers Believe About Names.

That could be worked around with a custom handleSignUp() controller method, but that method's logic is somewhat complex and it would be hard to keep the custom method updated as the framework evolves.

I propose including an option to use only a "name" field, which would be the name the person wants to be called. This is different from the user name. For instance, a woman with full name "Maria Aparecida da Conceição da Silva e Souza" could choose "Cida Conceição" or "Maria Aparecida Silva e Souza".

This "single name" option would be used in applications where it's irrelevant to try to split names in "first" and "last" parts.

When the option is disabled (the default), everything would be as it is now, preserving compatibility and familiarity with the English culture.

[mikesname]

+1

[pichsenmeister]

+1