Support lists

[jjlee]

Thanks for your recent work on orgparse, it looks promising.

It would be great if orgparse supported lists like this:

- one
- two
- three

I was able to port my code over from org-export-json to orgparse by parsing out the items from node.body myself, but I probably did a bad job of it, and that's exactly the sort of core org syntax thing that I'd love to be able to rely on orgparse for.

[karlicoss]

related: https://github.com/karlicoss/orgparse/issues/12 I'll think about it over the weekend!

[neilyio]

I second this! I often use orgmode un-ordered lists to take quick notes below a heading. Trying now to load these through orgparse, and I'm going to have to manually split them on newlines.

Great work on the package so far, I hope it can keep growing.

[MorphicResonance]

Lists support would be great. It is low level structural thing of org body/drawer. By the way extracting of user drawers would be great also.

[buhtz]

Mhm... While developing hyperorg using orgparse I understand orgparse not as a parser for org content. For me it is more a parser for metadata in org-files (e.g. the PROPERTIES section and the subtree structure, the filename).

I am not involved in the development of orgparse but I wonder if it would be a good idea to implement parsing of org content like paragraphs, lists, links, tables, etc. Maybe this is to much and would bind to much ressources in developing and maintaining. Maybe it would be a better idea to separate such a content parser into its own project and take care of good interoperability between that project and orgparse.

Currently I parse such (but currently not all) org-content-elements myself within my hyperorg project.