Closed david-waltermire closed 1 year ago
After investigating this, it looks like flexmark is generating the extra paragraphs.
Here is what the resulting node tree looks like:
Document[0, 48]
Paragraph[0, 20] isTrailingBlankLine
Text[0, 19] chars:[0, 19, "A1 aa … aaaaa"]
BulletList[21, 48] isTight
BulletListItem[21, 30] open:[21, 22, "*"] isTight
Paragraph[23, 30]
Text[23, 29] chars:[23, 29, "Item 1"]
BulletListItem[30, 39] open:[30, 31, "*"] isTight
Paragraph[32, 39]
Text[32, 38] chars:[32, 38, "Item 2"]
BulletListItem[39, 48] open:[39, 40, "*"] isTight
Paragraph[41, 48]
Text[41, 47] chars:[41, 47, "Item 3"]
I need to figure out how to suppress or filter this to fix it.
Thinking more about this, it might be better to allow the paragraphs, since in Markdown you can have many paragraphs in the list item.
For example:
first paragraph
second paragraph
So alternately, I could update the HTML binding to allow this.
I ended up adding support for tight list items in usnistgov/metaschema-java#159. This will work as described in this bug report once #150 is merged.
Describe the bug
A
oscal-catalog:listItemType
is incorrectly serialized into XML.Who is the bug affecting?
liboscal-java
users that serialize into XML and the input OSCAL instance contains aoscal-catalog:listItemType
node.What is affected by this bug?
The serialized XML output is invalid, as it does not conform to the released OSCAL XSD.
When does this occur?
When serializing
oscal-catalog:listItemType
node into XML.How do we replicate the issue?
OscalBindingContextTest.testLoadCatalogXml(@TempDir Path tempDir)
to:Given
Input
Notting XSD validation of input
Actual
Output
Validation output
Expected behavior (i.e. solution)
Output that aligns with the markup-multiline documentation and matches released OSCAL XML Schema.
Other Comments
None