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
If one forgets a "," in dependencies list (if I remember well what the issue was there), they get error like the following one. Similar errors occur if one misses "," in JSON at other places.
Also similar errors (instead of some useful message pointing to where the parsing problem is) occur if one places Javascript comments in JSON (seems the spec doesn't support that thing at all, whereas XML files can have comments) from what I remember
at "boss update" command (the case here was either a missing "," in a JSON array, or that in some packages I had an outer wrapping "package" node in the JSON (had found that from the web and discussing with copilot since I don't see any JSON Schema available for boss.json files to be able to validate them [and learn their syntax by checking out the schema - for examples I had tried searching for boss.json on github repos, but had found various syntaxes being used and also some other boss.json unrelated files [from other s/w])
in any case need more robust JSON parsing with detailed info on where error is. Or create a JSON schema (useful by itself anyway) and include a validation step (assuming there are json-schema libraries for Go) before trying to parse it with the current "quick & dirty" way)
The text was updated successfully, but these errors were encountered:
If one forgets a "," in dependencies list (if I remember well what the issue was there), they get error like the following one. Similar errors occur if one misses "," in JSON at other places.
Also similar errors (instead of some useful message pointing to where the parsing problem is) occur if one places Javascript comments in JSON (seems the spec doesn't support that thing at all, whereas XML files can have comments) from what I remember
in any case need more robust JSON parsing with detailed info on where error is. Or create a JSON schema (useful by itself anyway) and include a validation step (assuming there are json-schema libraries for Go) before trying to parse it with the current "quick & dirty" way)
The text was updated successfully, but these errors were encountered: