ENUM fields for rules #2

New Issue

florian · 2024-02-06T15:11:07+01:00

florian commented

2024-02-06 15:11:07 +01:00

As was pointed out in our most recent discussion about the direction of this project it would be a great addition if some fields could implement a set of allowed values that will be used twofold:

Inside of Generate() this method can be used to check whether the values coming from the consumer are plausible.
The GET /rule/:rule endpoint will now present the possible ENUM values, which will allow in a better user interface on the client side (ie Dropdowns with only ENUM values)

Implemented thoroughly, this will allow better backend plausibility of values provided, and allow a more userfriendly way of displaying fields where only a set of answers if allowable.

As was pointed out in our most recent discussion about the direction of this project it would be a great addition if some fields could implement a set of *allowed values* that will be used twofold: * Inside of `Generate()` this method can be used to check whether the values coming from the consumer are plausible. * The `GET /rule/:rule` endpoint will now present the possible ENUM values, which will allow in a better user interface on the client side (ie Dropdowns with only ENUM values) Implemented thoroughly, this will allow better backend plausibility of values provided, and allow a more userfriendly way of displaying fields where only a set of answers if allowable.

florian referenced a pull request that will close this issue

2024-02-06 21:22:28 +01:00

✨ integrates Dynamic ENUM Metadata within Rules #3

florian changed title from ~~Dropdown Felder~~ to ENUM fields for rules

2024-02-06 21:23:00 +01:00

florian closed this issue

2024-02-06 21:52:00 +01:00

florian referenced this issue from a commit

2024-02-06 21:52:02 +01:00

✨ integrates Dynamic ENUM Metadata within Rules (#3)

Sign in to join this conversation.