Skip to content

Improve error message when no valid task is found #498

@fjtirado

Description

@fjtirado

Currently for workflows that are not compliant with the spec, a long stack trace is printed as natural result of a failed parsing.
This long stack trace contains details of the failure, but they are expressed as java exception, which are sometimes difficulty to interpret.
It would be better (sacrificing some perfomance to increase usabillity) to validate the file againts the DSL schema before proceeding with the parsing. The validation will give the user, in one shot, all the format errors.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy