Skip to content

Surface Validation Errors as Issues with Specific Lines #350

@bencap

Description

@bencap

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.

Metadata

Metadata

Assignees

Labels

app: backendTask implementation touches the backendapp: frontendTask implementation touches the frontendtype: enhancementEnhancement to an existing feature

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions