demo/validator
1
0
Fork 0
mirror of https://github.com/itplr-kosit/validator.git synced 2026-05-25 16:55:39 +00:00
Code Issues Projects Releases Packages Wiki Activity

Fix the options table in docs/cli.md

Browse source
This commit is contained in:
Ahmed Zaki 2025-02-27 15:05:51 +02:00 • committed by GitHub
parent 5184f86c5e
commit ab7fe46728
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/cli.md
View file

@ -46,11 +46,12 @@ java -jar validationtool-<version>-standalone.jar -s "NAME1=<scenario-config-fi
Besides the obvious functionality of validating, the cli provides additional functionality to customize the processing: Besides the obvious functionality of validating, the cli provides additional functionality to customize the processing:
|name | option | description | | - | - | - | | [Daemon mode](daemon.md) | `-D` | Starts the validator in daemon mode as an HTTP service | | | name | option | description |
print mode | `-p` | Print the report to stdout | | extract html | `-h` | Extracts any html blocks within the report and saves the content to | - | - | - | | [Daemon mode](daemon.md) | `-D` | Starts the validator in daemon mode as an HTTP service |
the filesystem. Note: the file name is derived from the node name the html appears in | | print memory stats | `-m` | Prints some memory | print mode | `-p` | Print the report to stdout |
usage information. Mainly for debugging purposes on processing huge xml files | | check assertions | `-c <file>` | Check assertions on the | extract html | `-h` | Extracts any html blocks within the report and saves the content to the filesystem. Note: the file name is derived from the node name the html appears in |
generated reports. This is mainly useful for scenario developers. Ask KoSIT for documentation, if you want to use this feauture | | print memory stats | `-m` | Prints some memory usage information. Mainly for debugging purposes on processing huge xml files |
| check assertions | `-c <file>` | Check assertions on the generated reports. This is mainly useful for scenario developers. Ask KoSIT for documentation, if you want to use this feauture |
## Return codes ## Return codes