Undocumented HTML Sub-Collection Import

[bryanhunwardsen]

Is your question related to a problem or code? Please describe.
Short of putting it in a live debugger, I tried manually walking the algorithm in importFromHTMLFile.ts and between its multi-layer processing and recursion. I was not able to construct a simple HTML for import that would create nested sub-collections and the links intended to go into each level.

I searched online and didnt find any viable solution that would parse as desired on import.

Would you kindly post a sample HTML that can import the following structure:

I tried crafting several (simpler) variations of the above described nesting/links, the best I could do is get all collections created, none nesting properly, and some but not all links created in either their target collection or in Imported, although since no collection could be nested, I was unable to fully test this.

I also manually created the above test-tree from the UI then exported the json to reverse engineer it, it did not export as expected, a couple notes:

• Collections do not export with their internal Id only their parentId, while you can infer the collection id from the value in any of the child link nodes, this is clumsy and wouldnt work in an empty collection. It would be better if the id is included in the collection properties itself.
• Sub-collections are exported flatly while links are exported nested. The organization and format would be much cleaner if the links were exported flat as well, this would enable gmail like tagging functionality where a single link could be assigned into multiple collection/sub-collections. This would require an enhanced modify/delete to apply to selected/all tags, which then allows bifurcation of the same url into different collections whereby collection specific metadata could be applied. But also could be as simple as: Delete from this Collection or Delete from all collections prompt.

Include any code or screenshots (if applicable)
N/A

Additional context
N/A