find
--findv1.0.0`find` command parser
Linuxcommand
$ cat input.txt | jc-rs --findA real pair
From the reference corpus (ubuntu-18.04/find.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.
findubuntu-18.04
. ./ ./jc ./jc/tests ./jc/tests/test_find.py ./jc/tests/test_history.py ./jc/tests/test_hosts.py ./jc/anotherdirectory find: './inaccessible': Permission denied ./jc/directory2 ./jc/directory2/file.txt ./jc/directory2/file2.txt ./newfile.txt
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
[ { "path": null, "node": "." }, { "path": ".", "node": null }, { "path": ".", "node": "jc" }, { "path": "./jc", "node": "tests" }, { "path": "./jc/tests", "node": "test_find.py" }, { "path": "./jc/tests", "node": "test_history.py" }, { "path": "./jc/tests", "node": "test_hosts.py" }, { "path": "./jc", "node": "anotherdirectory" }, { "path": null, "node": null, "error": "find: './inaccessible': Permission denied" }, { "path": "./jc", "node": "directory2" }, { "path": "./jc/directory2", "node": "file.txt" }, { "path": "./jc/directory2", "node": "file2.txt" }, { "path": ".", "node": "newfile.txt" } ]
Fixture coverage
2/2oracle-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/find.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