Surface Validation Errors as Issues with Specific Lines #350
Labels
app: backend
Task implementation touches the backend
app: frontend
Task implementation touches the frontend
type: enhancement
Enhancement to an existing feature
Many validation errors are currently surfaced as a result of a failed
if not all(..)
check. This results in generic error messages with no hint to the user as to which variant(s) are problematic.The user experience would stand to improve if such errors were surfaced on a line-by-line basis, so that users who upload data and experience such validation errors can fix them expediently and have a better sense of what the issue is.
The text was updated successfully, but these errors were encountered: