argilla icon indicating copy to clipboard operation
argilla copied to clipboard

Custom validations in Feedback Datasets

Open nataliaElv opened this issue 1 year ago • 7 comments

Is your feature request related to a problem? Please describe. As an admin, I would like to set up custom validations for a Feedback Dataset, for example: if a user gives a response to question x, then question y should have an answer; labels x & y in MultiSelect questions are incompatible; no question is required but at least 1 should have an answer...

Describe the solution you'd like When creating a FeedbackDataset pass a function or set of functions defined by the user as an argument. These will have a custom validation and error messages. These will run whenever the user tried to submit a form and the error message(s) can be displayed as a toast.

Describe alternatives you've considered Enabling/disabling questions following an ITTT workflow is an option, but perhaps this cannot cover all of the possible scenarios e.g. having no required question but needing at least an answer to one of them.

Additional context Add any other context or screenshots about the feature request here.

nataliaElv avatar Jun 05 '23 09:06 nataliaElv

Does that mean that the question y should be disable to the user until the question x have an answer ?

keithCuniah avatar Jun 05 '23 09:06 keithCuniah

We should think about this carefully, but yes, probably we want to disable/enable questions given certain conditions.

nataliaElv avatar Jun 07 '23 08:06 nataliaElv

#3112

nataliaElv avatar Jun 07 '23 11:06 nataliaElv

This issue is stale because it has been open for 90 days with no activity.

github-actions[bot] avatar Sep 06 '23 01:09 github-actions[bot]

@nataliaElv I believe #3112 is a different issue right?

davidberenstein1957 avatar Oct 10 '23 08:10 davidberenstein1957

Yes it's different. I just mentioned it here because it was created after the discussion we had above.

nataliaElv avatar Oct 10 '23 08:10 nataliaElv

This issue is stale because it has been open for 90 days with no activity.

github-actions[bot] avatar Jan 09 '24 01:01 github-actions[bot]

This issue was closed because it has been inactive for 30 days since being marked as stale.

github-actions[bot] avatar Jul 27 '24 01:07 github-actions[bot]