Skip to content
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

Validation of YAML #176

Closed
jsavage opened this issue Oct 12, 2022 · 1 comment
Closed

Validation of YAML #176

jsavage opened this issue Oct 12, 2022 · 1 comment
Assignees
Labels

Comments

@jsavage
Copy link

jsavage commented Oct 12, 2022

Hi @jonasthewolf
Maybe its just my inexperience working with JSON but as my GSN network grows so does the challenge of validation.
My experience of using other tools for this is mixed. I am using visual studio code out of the box for editing and have been trying the YAML validator from jsonformatter.org. However, this recently proved inadequate against a very noddy typo as shown at the bottom of the page. Other validators such as http://www.yamllint.com/ also failed to detect this so perhaps I am expecting too much from those tools.

I do think others who try gsn2x would value some advice on this topic - even if that is just a few links to freely available tools or some suggested validation rules that can be added to the likes of VSC or Notepad++ or another widely used editor.

The other thought I had when debugging this was whether the accuracy of the line number reported in this type of error message could be improved - especially when it relates to invalid YAML like that causing this error.
image

Although I can now see the cause, as you can see, the YAML was still showing as valid.
image

@jonasthewolf jonasthewolf self-assigned this Oct 12, 2022
@jonasthewolf
Copy link
Owner

Hi @jsavage, again this is the same issue as #74.
The root cause in rust/serde was closed and recently re-opened here: serde-rs/serde#2157
Let's hope that we get that fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants