Skip to content

DOCS-i18n: Select among alternative text translations #22522

@narthur157

Description

@narthur157

I'm submitting a...

[x ] Documentation issue or request

Current behavior

The text in the docs does not match the example code given

Expected behavior

They should match

Minimal reproduction of the problem with instructions

image
The following format message in the component template binds to the component's gender property, which outputs one of the following string values: "m", "f" or "o". The message maps those values to the appropriate translations:

Referring to the example:

The author is {gender, select, male {male} female {female} other {other}}

What is the motivation / use case for changing the behavior?

Unless I am quite confused, it seems like the component should be said to be outputting "male", "female" or "other". If I am confused, then perhaps the docs should be clearer here..

Suggested new docs text:
The following format message in the component template binds to the component's gender property, which outputs one of the following string values: "male", "female" or "other". The message maps those values to the appropriate translations:

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions