KSC warnings are perceived as errors

[KOLANICH]

Such unneeded and undisableable warnings as violations of the badly-designed style guide.

[hello-adam]

Are you talking about the kaitai plugin naively printing ksc output? What style guide are you referring to?

[KOLANICH]

Latest (nightly) versions of KSC contain a built-in linter that emits warnings when a creator of a spec has violated the style guide.

[hello-adam]

Ah, ok, you're saying that if there's stderr output from KSC, the hobbits plugin should not bomb out (it should wait to see if there is a generated ".py" parser file.)

[KOLANICH]

Why not to use the information in structured JSON form? In CLI backend for kaitaiStructCompile I use that, works fine.

[hello-adam]

can you give an example of the --ksc-json-output JSON output that has the warning in a section that will be distinct from errors? Maybe also an example of how failure condition errors will look?

[KOLANICH]

Currently it doesn't emit any warnings into JSON repr at all.
Errors look like:

{"./lto.ksy": {"errors": [{"file": "./lto.ksy","path": ["seq","8"],"message": "string type, but no encoding found"}]}}

[hello-adam]

let me know if b2fafbf solves this for you. I was able to test with error and non-error conditions, but I don't have a nightly build of ksc to test the warning situation (also, I'm not sure how robust my parsing of the errors is...)

[KOLANICH]

Yeah, that works. I had to rebase it over master though because devel is still broken - it doesn't detect plugins properly.