Topics with content + subtopics

[thusithaC]

Even though it might not be best practice, there is markdown which follow below format.

value = """
# Description

This is an example file

## Authors

* Nate Vack
* Vendor Packages
    * docopt
    * CommonMark-py

## Versions

### Version 1

Here's something about Version 1; I said "Hooray!"

### Version 2

Here's something about Version 2

"""

When this is jsonified, the content under the main topic This is an example file gets lost.

'{"Description": {"Authors": ["Nate Vack", "Vendor Packages", ["docopt", "CommonMark-py"]], "Versions": {"Version 1": "Here\'s something about Version 1; I said \\"Hooray!\\"", "Version 2": "Here\'s something about Version 2"}}}'
Is there a good way of handling this situation?

[njvack]

What behavior would you suggest?

[thusithaC]

I think what I'm requesting is "not following the CommonMark standard" The problem is that in the standard, https://spec.commonmark.org/0.29/#container-blocks a block could either be a leaf block or a container block. It expects a container block to be purely containing other blocks, but not content. I'll have to find another solution to handle markdowns with mixed blocks (something like a tree structure with a custom defined Nodes) Thanks,

…

On Sun, Jul 28, 2024 at 11:24 AM Nate Vack ***@***.***> wrote: What behavior would you suggest? — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVRIJ4KK2WVQRNQJZ5Y53TZORB4TAVCNFSM6AAAAABLRGUEPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGMYDGNRRGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Thusitha Chandrapala

[njvack]

Yeah, there's no standard for doing this transformation. There's a huge amount of valid markdown that doesn't have a reasonable translation to json.

I will very much go on the record saying I generally don't think anyone should use this package ;-)