Currently to use fy-tool --tsv-event you also need --testsuite.
When I asked for the tsv output, it had nothing to do with the test suite, even
though that output is also one event per line.
The purpose of tsv was for writing a loader/composer using fyaml by just
reading stdin rather than needing to do a formal C binding.
This could be useful for all sorts of things, and honestly we might do well to
make this into a separate binary called bin/yaml-parse-events at some point.
Also it's a bit wrong to have --testsuite as the option for events formatted
for testing with the suite. In the future we will likely have other tests in
the suite besides parse events.
My suggestions at this point would be:
--mode=events-tsv
--mode=events-testsuite
You can keep --testsuite as an alias for --mode=events-testsuite.
I'd also like the events-tsv output to add a =ERR output line when a parse
error occurs. It should contain the line position numbers and the error
message.
That way a loader built over it could handle/format the error as it sees fit.
This would be cleaner than the loader having to capture an actual parse error
from fy-tool.
Note: This =ERR should not be added to the events-testsuite output.
Currently to use
fy-tool --tsv-eventyou also need--testsuite.When I asked for the tsv output, it had nothing to do with the test suite, even though that output is also one event per line.
The purpose of tsv was for writing a loader/composer using fyaml by just reading stdin rather than needing to do a formal C binding. This could be useful for all sorts of things, and honestly we might do well to make this into a separate binary called
bin/yaml-parse-eventsat some point.Also it's a bit wrong to have
--testsuiteas the option for events formatted for testing with the suite. In the future we will likely have other tests in the suite besides parse events.My suggestions at this point would be:
--mode=events-tsv--mode=events-testsuiteYou can keep
--testsuiteas an alias for--mode=events-testsuite.I'd also like the events-tsv output to add a
=ERRoutput line when a parse error occurs. It should contain the line position numbers and the error message.That way a loader built over it could handle/format the error as it sees fit. This would be cleaner than the loader having to capture an actual parse error from fy-tool.
Note: This
=ERRshould not be added to theevents-testsuiteoutput.