Closed IdkGoodName closed 2 years ago
there seems to be some conflicts, but thanks for pointing that the nested list display was not working as intended because of the Descendants
instead of Elements
call in the extensions! There was no need for specific code in the ListElement
class as the recursion handling is automatic through the AppendAsMarkdown
method (it just needed to initialize correctly the GetElementWriters
of the tester and put the nested <list>
inside the <item>
).
Still interested in the <term>
!
I could remove the sub-list implementation and just leave out the term then
Should I even update this PR?
Yes fell free to do it, I am done with the big refactoring and just need to add xml comments to the Api library before the next version so there shouldn't be any big conflicts from now on.
Sorry for basically stretching this out for a month.
oh no it's me who kept making big changes with all kind of conflicts haha
Is it ready for merge or what does need to be changed?
not sure why there's some conflict, I will try to merge it manually (sorry wasn't really available in the past weeks).
Finally got around to merge it. I hope it's ok for you after rereading the microsoft documentation for list I changed a little the implementation for table (listheader
should only contains term
s and item
only description
s).
Adds support for
<term>
tag and allows the creation of sub-lists. Em-dash(—
) is used to separate the term and the description. If either of them is not present, em dash is not added.Outputs: