You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a data file is mapped to a schema ID which does not exist, rather than exiting with an error code of 1 and printing a failure message to the screen, schema-enforcer prints a message to the screen indicating that all schema validation checks have passed when the command schema-enforcer validate is run. The non-existent schema IDs still show up when the command schema-enforcer validate --show-checks is run. Functionality should be implemented in the tool such that:
A log message is printed indicating that the referenced schema-id can not be found when the command schema-enforcer validate is run. The tool should also exit with a code of 1.
The same should occur when the schema-enforcer validate --show-checks or schema-enforcer validate --show-pass commands are run.
The text was updated successfully, but these errors were encountered:
When a data file is mapped to a schema ID which does not exist, rather than exiting with an error code of 1 and printing a failure message to the screen, schema-enforcer prints a message to the screen indicating that all schema validation checks have passed when the command
schema-enforcer validate
is run. The non-existent schema IDs still show up when the commandschema-enforcer validate --show-checks
is run. Functionality should be implemented in the tool such that:schema-enforcer validate
is run. The tool should also exit with a code of 1.schema-enforcer validate --show-checks
orschema-enforcer validate --show-pass
commands are run.The text was updated successfully, but these errors were encountered: