translation.too_many_selectors: A message has more than one enum or plural field

A message has more than one enum or plural field.

Area 10, Configuration; not declinable; the next step is usually the agent's.

An enum field gives one wording for each of its values and a PluralCount field one for each plural form; together they would be a grid for a translator to fill.

example

use shipping/types { Formality }/// A combo of wordings.type Combo = Message {    formality: Formality    count: PluralCount}

jadpo checkcheck failed: 1 error, 3 files

error Combo has two fields that choose its wording, formality and count

--> domains/shipping/translations/combo.jadpo:6:5

  |5 |     formality: Formality  |     --------- the first6 |     count: PluralCount  |     ^^^^^ a second choice

reason: An enum field gives one wording for each of its values, and a PluralCount field one for each plural form of the language. Both at once would need a wording for every pairing of a value and a form, which a translator would have to fill in.
next: Split Combo into two messages, one for each choice, and call both (agent)
rule: translation.too_many_selectors
help: https://jadpo.dev/docs/errors/translation.too_many_selectors