DJORNL parser: more dry_run options
#56
Comments
dakotablair
added a commit
to dakotablair/relation_engine
that referenced
this issue
Oct 27, 2020
This commit adds the --dry-run parameter to validate the input data and print an output summary even in the presence of errors. To this end, the --output parameter is also introduced to give an option to display the summary as JSON or in a more user-friendly text format. The --debug parameter will repeat the full list of errors when there are any at the end of the run. Errors are now printed to stderr and may be surpressed using shell redirection.
dakotablair
added a commit
to dakotablair/relation_engine
that referenced
this issue
Oct 28, 2020
This commit adds the --dry-run parameter to validate the input data and print an output summary even in the presence of errors. To this end, the --output parameter is also introduced to give an option to display the summary as JSON or in a more user-friendly text format. The --debug parameter will repeat the full list of errors when there are any at the end of the run. Errors are now printed to stderr and may be surpressed using shell redirection.
dakotablair
added a commit
to dakotablair/relation_engine
that referenced
this issue
Nov 19, 2020
This commit fixes issue kbase#56 by adding the --dry-run parameter to validate the input data and print an output summary even in the presence of errors. To this end, the --output parameter is also introduced to give an option to display the summary as JSON or in a more user-friendly text format. Data should not be loaded if there are errors or if this command is invoked with --dry-run.
dakotablair
added a commit
to dakotablair/relation_engine
that referenced
this issue
Nov 20, 2020
This commit fixes issue kbase#56 by adding the --dry-run parameter to validate the input data and print an output summary even in the presence of errors. To this end, the --output parameter is also introduced to give an option to display the summary as JSON or in a more user-friendly text format. Data should not be loaded if there are errors or if this command is invoked with --dry-run.
dakotablair
added a commit
to dakotablair/relation_engine
that referenced
this issue
Nov 20, 2020
This commit fixes issue kbase#56 by adding the --dry-run parameter to validate the input data and print an output summary even in the presence of errors. To this end, the --output parameter is also introduced to give an option to display the summary as JSON or in a more user-friendly text format. Data should not be loaded if there are errors or if this command is invoked with --dry-run.
dakotablair
added a commit
to dakotablair/relation_engine
that referenced
this issue
Nov 23, 2020
This commit fixes issue kbase#56 by adding the --dry-run parameter to validate the input data and print an output summary even in the presence of errors. To this end, the --output parameter is also introduced to give an option to display the summary as JSON or in a more user-friendly text format. Data should not be loaded if there are errors or if this command is invoked with --dry-run.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dry_runoption so that it can be called from the command line, e.g.alter the implementation of
dry_runso that it prints dataset statistics and a list of errors, rather than dying with a list of errors without reporting stats.print out the stats in a more user-friendly manner
The text was updated successfully, but these errors were encountered: