crontab-u
--crontab-uv1.10.0Converts `crontab` file with user field to JSON
filecommand
$ cat input.txt | jc-rs --crontab-uA real pair
From the reference corpus (generic/crontab-u-no-normal-entries.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.
crontab_ugeneric
#this is a test for the jc module @daily root /bin/sh do_the_thing
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
{ "variables": [], "schedule": [ { "occurrence": "daily", "user": "root", "command": "/bin/sh do_the_thing" } ] }
Fixture coverage
5/5oracle-valid pairs match under the published structural JSON comparison
Magic syntax
not availableThis parser reads a file or a string rather than a command, so there is nothing for jc-rs to run. Pipe it in.
Source: crates/jc-rs-parsers/src/misc/crontab_u.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare