Feature idea: Per-field validation for multiple_text

[wardi]

• need to decide how to report multiple errors and highlight the correct fields in the form
• do we allow customization of the validation or create a bunch of separate presets multiple_url, multiple_email and so on

[ccancellieri]

Hi I like your work this is why we're working on a customization of this field for our DCAT because:

1. can't add 2 of this since the <+ add> search by class so it get confused [bug fixed changing JS and snippet]
2. we changed the layout of the help field which was duplicated [fixed]
3. we noted that using API (via form multipart) it's mandatory to send a value (even an empty one) otherwise the sqlachemy insert query will complain [bug still not fixed]

Do you prefer to talk about those issues or it's ok to discuss them here?

What we've planned to do on our (custom) component: we will introduce completion and validation (for some of them we need a dictionary for some other we need slug to datasets and some other to distributions)

I think that the validator list can be passed as param to the multiple text or (better in my opinion) we can pass a field (or a preset) to use as child into the multiple_text so we can handle all the autocompletion and the validation field into the nested preset and just pass them to the (container preset) multiple_text which may only handle simple constraints like Min/Max occurrences and optional

[wardi]

Please open separate issues or PRs for 1, 2, and 3, this one is just for per-field validation of multiple_text. I'm happy to review fixes in PRs if you're already working on them.