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
As an OSCAL developer, I would like to be able to handle violations when using the DESERIALIZE_VALIDATE_CONSTRAINTS feature when deserializing a node item. For example when loading a profile to resolve (as per test), it currently will log an error if the source file has violations . But the returned OscalInstance does not contain any information regarding any violations.
Goals:
The information regarding existence of violations is returned as either an exception or included in the returned context.
Dependencies:
None
Acceptance Criteria
All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
The text was updated successfully, but these errors were encountered:
It would also be useful to force a failure if the file is found to be invalid. This could be handled by a new feature on the document loader/deserializer. Consider making this feature the default behavior.
User Story:
As an OSCAL developer, I would like to be able to handle violations when using the
DESERIALIZE_VALIDATE_CONSTRAINTS
feature when deserializing a node item. For example when loading a profile to resolve (as per test), it currently will log an error if the source file has violations . But the returned OscalInstance does not contain any information regarding any violations.Goals:
Dependencies:
None
Acceptance Criteria
The text was updated successfully, but these errors were encountered: