Open billbarsch opened 9 years ago
That's interesting. I like the way you think. That certainly would be easier.
However... it seems to go against the design of Alpaca (as a forms generator around JSON schema). Wherein 100% of the form schema validation (allowed values, etc) is derived from the underlying JSON schema. In this case, the schema doesn't say anything about the allowed values. The data provided shouldn't necessarily force the schema, if you know what I mean.
Need to give it some thought as I think it'd be much easier. But it might encourage some practices that deviate from what is ideally supported by the tool.
What do you think? Cool idea and apart from the JSON schema mindset, I'm otherwise in agreement.
Something like this should be possible:
to create radio/checkbox inputs like tihs:
The enum requeriment should be optional.
Ex: I have a alpaca table field to show some data like "my email box" If I need to put a checkbox to "select" my "emails", and put the database "id" at the checkbox "value", I can't do this because checkboxes requires enum.