NEWS.md

loggit 2.1.1

This is a small bugfix release for CRAN's sake that fixes two tests that would sporadically fail; they relied on timestamps being equivalent between want and got invocations.

loggit 2.1.0

Sanitizers are functions allow for custom replacements of invalid (nd)JSON characters in the submitted log data. Unsanitizer functions perform the opposite action: replacing sanitized output with their original values when read back inttohe R session. If not provided, loggit() and read_logs() will invoke the default sanitizer table, which (currently) maps string replacements as follows:

| Character | Replacement in log file | |:--------- | :---------------------- | | { | __LEFTBRACE__ | | } | __RIGHTBRACE__ | | " | __DBLQUOTE__ | | , | __COMMA__ | | \r | __CR__ | | \n | __LF__ |

Users may specify their own (un)sanitizers as functions that take & return single strings, though they are regardless encouraged to not include invalid characters in the logs in the first place. Please refer to the documentation for more details.

loggit 2.0.1

loggit 2.0.0

Please note that this change means that log entries should not contain any embedded newline characters (\r, \n, or \r\n), as this will break the logging format of the file. Your logs will still be written (with a base::warning), but parsing the data with external tools or the included read_logs() function may not behave correctly. loggit could one day enforce these content rules internally, but the decision for now is to stay out of the way of the user code generating the logs, and put the onus of correction on the developer.

Note that despite the significant backend behavioral changes presented here, the user-facing API for this package has changed very little (documented below).

loggit 1.2.0

loggit version 1.1.1

loggit version 1.1.0

loggit version 1.0.0



Try the loggit package in your browser

Any scripts or data that you put into this service are public.

loggit documentation built on Feb. 28, 2021, 9:06 a.m.