Can’t distinguish programmatically between snapcraft.yaml errors and other errors

[Matthew Paul Thomas]

Apologies for the incomplete bug report.

snapcraft may return an error because of a problem with the snapcraft.yaml (for example bug 1578024), or it may fail for other reasons (for example bug 1624019)

Evan says that currently, there is not a programmatic distinction (such as an error code) between these two kinds of error. This would be helpful in build.snapcraft.io, so that snapcraft.yaml-specific errors can be attached to the snapcraft.yaml UI.

[Cris Dywan (kalikiana)]

Perhaps different error codes depending on the exception would be the obvious option.

Or the proposed "snapcraft lint" could be used to check validity in a preliminary step.

[Cris Dywan (kalikiana)]

This can actually be implemented now by adding get_exit_code to error subclasses in snapcraft/internal/errors.py