-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught yaml.composer.ComposerError with undefined alias with 'fmf show' #50
Comments
Similar thing happens with undefined default:
|
So, if I understand that correctly, we get traceback if the yaml file is not valid, right? When alias is properly defined, data are set as expected:
gives:
and
gives:
What do you propose? To have a shorter error message? The traceback gives some nice details about where the YAML syntax problem is. |
Yes, these situations are using invalid yaml file with undefined alias / default. You can get here either by forgetting to define those or as I did by not knowing of those and accidentally using the symbols */&. :) We have basically 4 situations here:
These produce:
Now the proposition here depends on the exact situation:
This whole issue is really corner case, so treat it with low priority :) |
I've updated exception handling to cover all yaml errors and also covered the special |
The text was updated successfully, but these errors were encountered: