-
Notifications
You must be signed in to change notification settings - Fork 4
Coverage report and test coverage improvements #141
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
Conversation
…lternate file stream refactor: allow passing log config through to the parser test: add test for trace logging of parser events fix: fix output of YAML scalar events that could potentially overflow fix: fix printing of filename in logs when the library is built in a build subdirectory (strip leading ../)
type of the value so it doesn't have to be re-inferred from the raw fy_node test: improve test coverage on value.c
Not as flexible as a custom formatter but that's not a path I want to bother going down right now. test: fixes the logging test to not include line numbers in the expected log output considering what a pain in the ass that would be to maintain
… in some pathologically formatted files test: increase test coverage--these tests exposed some of these bugs
not really noted as a "feature" yet since it's undocumented
|
According to Update: Oh, I just forgot that |
use asdf_event_iterate instead of asdf_parser_parse; the latter is lower-level--it just parses until the next event and returns the event; asdf_event_iterate is basically the same but it automatically frees the previous event on each call
|
Wanted to see if I could build coverage reports in the CI but had some trouble. For now I'd like to just get this merged for the fixes it includes and can come back to the CI question later. |
Spent a little time over the holidays adding more tests and improving overall coverage. Fixed a few bugs in the process and added new log-formatting features to boot.