Problem:
The one-of constraint provides a list of values that should be used with a property like "sex or gender". This list can be ordered by the editors based on a criteria like which values are most like to be used. "Male" and "Female" are listed first for example for "sex or gender".
When using the one-of constraint to make value suggestions in new statements this order is not respected and the values are suggested more or less randomly. This leads to "female" being one of the last suggestions for example. The suggestions should follow the order on the constraint definition.
Example:
BDD
GIVEN a property with a on-of constraint
WHEN creating a new statement with that property
THEN the suggestions are in the same order as they are on the constraint definition
Acceptance criteria:
- When adding a new statement the order of the suggested values is the same as the order of the values in the definition of the one-of constraint