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
Is it worthwhile to add helper functions for adding or extracting nodes? There is an issue around namespaces, which can be tricky. Things I think could be on the docket to add:
code chunks
lists
tables
The namespace thing is tricky, should your PR actually add a helper function for adding childs (and siblings and parents?)? The arguments would be everything but not the namespace, that tinkr would set. The function would also check the text ends with a newline, if there's text.
I think adding helper functions for these situations would be quite nice. The only thing is that the code block example is one of the simplest situations because you only need the code block and the text that goes inside. It gets more complex with almost any other element.
One avenue we might explore is having a helper function that inserts user markdown as nodes by passing it through commonmark::markdown_xml() and then taking the children of that new document. That's was one of the strategies I found to work with dealing with list elements in {pegboard}
Is it worthwhile to add helper functions for adding or extracting nodes? There is an issue around namespaces, which can be tricky. Things I think could be on the docket to add:
I think adding helper functions for these situations would be quite nice. The only thing is that the code block example is one of the simplest situations because you only need the code block and the text that goes inside. It gets more complex with almost any other element.
One avenue we might explore is having a helper function that inserts user markdown as nodes by passing it through
commonmark::markdown_xml()
and then taking the children of that new document. That's was one of the strategies I found to work with dealing with list elements in {pegboard}Originally posted by @zkamvar in #24 (comment)
The text was updated successfully, but these errors were encountered: