You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Although I can now see the cause, as you can see, the YAML was still showing as valid.
The text was updated successfully, but these errors were encountered:
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.
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.

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

The text was updated successfully, but these errors were encountered: