Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
1) Form validation
Is it possible to validate form inputs?
For a start, checking if empty (so basically making inputs required) would be enough for me. Especially that I've noticed that the new [component:input-select] already notify users that it's required when left empty.
Unfortunately, all the other form tags either allow empty inputs or throw an error (number tag for example).
2) Data binding options
Why is it possible to bind Value and Input Destination to layers tagged as [component:input-x]? Meaning, what's the use case for it?
I've been trying to bind data through Value as an input placeholder that could be then sent using Input Destination but unfortunately, I wasn't able to make it work yet.
Edit: I finally figure it out - one use case I was able to make work is Patch request (editing). So first I bind Values (from the Details) and then I submit my changes through the Input Destination.
Previously I was using Values from a completely different Airtable table using separate a request so maybe the problem was somewhere there. I will try it again when I will have a moment.
3) Form structure
To figure this one out, it really took me at least a few hours.
It seems that it's required to have [action:submit] in the same [container] as the rest of the form to make it work but I don't think it's really mentioned anywhere in the documentation or YouTube tutorials.
When submit and inputs are in different containers, the result of the submit will be an empty row (might be a reason for this post) which means that something like this is not possible:
- form [container]
- inputs go here
- floating-action [layer]
- button [action:submit]
1 reply
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord