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
The new version of oscal-cli does not attempt to pretty print the conversion result, as this can be rather problematic, as seen by this issue. Since the output is not pretty printed, this issue is no longer a problem.
The new version of oscal-cli does not attempt to pretty print the conversion result, as this can be rather problematic, as seen by this issue. Since the output is not pretty printed, this issue is no longer a problem.
As in: you recommend this be closed as WONTFIX because we will not try to align the output at all anymore? I want to make sure I understand, but I can definitely agree with that approach. Disregard, I saw updated communication on issue and PR tracking. It addressed this question.
Describe the bug
liboscal-java
provides different indentation to XSLT output fromSaxon
.Who is the bug affecting?
Users using both
liboscal-java
andSaxon
. Noting official project usage as outlined in the documentation.What is affected by this bug?
Indentation consistency.
When does this occur?
On profile resolution.
How do we replicate the issue?
Given the below input based on Saxon (latest release) formatting:
Actual:
Expected behavior (i.e. solution)
Consistency between the tools. See
<strong>
node in the below.Other Comments
The text was updated successfully, but these errors were encountered: