-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Exceptions on malformed yaml #37
Comments
Yes it will be user friendly |
@jayvdb @chfw |
looking from ruamel.yaml's change log and overview, it looks better. My instance is: if our unit tests above passes, I would give ruame.yaml a go. |
yup, it passes the test. |
If empty value is found in mobanfile, moban will report the line number of that. Closes moremoban#37
If empty value is found in mobanfile, moban will report the line number of that. Closes moremoban#37
If empty value is found in mobanfile, moban will report the line number of that. Closes moremoban#37
If empty value is found in mobanfile, moban will report the line number of that and the name of the file. Closes moremoban#37
If empty value is found in mobanfile, moban will report the line number of that and the name of the file. Closes moremoban#37
If empty value is found in mobanfile, moban will report the line number of that and the name of the file. Closes moremoban#37
If empty value is found in mobanfile, moban will report the line number of that and the name of the file. Closes moremoban#37
Interesting, pyyaml can denote error location
pyyaml==3.13 |
Yeah, pyyaml shows that in doc. It's quite strange that pyyaml doesn't give that to dev. |
Meaning to the exception? |
i mean that pyyaml doesn't give location in general, even though they provide it in exception. |
Hmm... i've read pyyaml api and it seems to provide point of each element but not so convenient. |
I forgot to add a template after a target
And got
I suspect there are a few other similar cases of exceptions when given malformed yaml. moban should explain which line is broken and why.
The text was updated successfully, but these errors were encountered: