Better Custom name display order

[veronoicc]

Description / 功能描述

The current name display system works and already gives a good few options. however, the custom option has a few flaws. With it it is for example not really possible to do "First name (nickname)", as when you do "%first_name% (%nickname%)" it will work correctly for people who actually have a first name and nickname in the database, but if you for example have someone who only has a first name but no nickname given, it will just display "NAME ()", which looks odd. This can be observed with many other formattings aswell.

Motivation / 动机

Currently conditional formatting is only possible with the given options, but not in the custom option.

Proposed Solution / 建议方案

Add a way to do conditional statements in the custom name formatting option.

Alternatives Considered / 备选方案

No response

Additional Context / 补充信息

No response

[naiba]

Thanks, this makes sense. The missing piece is the custom-format syntax.

Could you confirm which behavior you would prefer?

1. Minimal cleanup only: keep the current syntax, but automatically remove empty parentheses/brackets and normalize spaces when a token is empty.
2. Explicit conditional syntax, for example something like so optional parts are controlled by the format string.
3. Another syntax you would prefer.

I do not want to invent a syntax that later becomes hard to support or migrate.

[naiba]

Correction to the examples above: GitHub issue formatting ate the literal examples in my previous comment.

The two options I meant were:

1. Minimal cleanup only: keep the current %field% syntax, e.g. %first_name% (%nickname%), but automatically remove empty parentheses/brackets and normalize spaces when a token is empty.
2. Explicit conditional syntax, for example {nickname? (%nickname%)}, so optional parts are controlled by the format string.

Which direction would you prefer?

[veronoicc]

I would say the second syntax, since its also not that big of a change in my mind, since we aren't adding a complete new templating system and rather just a simple conditional system.

[naiba]

Implemented on main in 35699b1 (feat(vaults): support vault name display overrides).

Custom name display templates now support non-nested conditional blocks, for example:

%first_name% %last_name% {nickname? (%nickname%)}

The conditional segment is only rendered when the referenced field has a non-empty value, so contacts without a nickname no longer display empty parentheses. The same validation now applies to both the global preference and vault-level overrides.

CI passed for the change: https://github.com/naiba/bonds/actions/runs/27150553586