Minor update to show XML content with problem #12132
Conversation
When working with OVAL it is not difficult spend a lot of time trying to identify a typo or an incorrect syntax. This commit include a minor update to help developers to see which content was causing an exception. This is specially helpful when multiple OVAL files are changed. Signed-off-by: Marcus Burghardt <[email protected]>
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
|
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
|
Code Climate has analyzed commit 1e81165 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 40.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 59.4% (0.0% change). View more on Code Climate. |
|
I no longer have the files where this issue was hit and in a quick try I couldn't reproduce. |
Description:
When working with OVAL it is not difficult spend a lot of time trying to identify a typo or an incorrect syntax. This commit include a minor update to help developers to see which content was causing an exception. This is specially helpful when multiple OVAL files are changed.
Rationale:
Make developers lives easier.
Review Hints:
Please, don't worry trying this PR right now.
I did this change when working on some more complex rules.
It happened when I tried some Jinja2 variables with OVAL objects but no longer have the information to reproduce it now.
I will come back to this PR in another opportunity to review it. For now I only documenting the change.