tight horizon
This spans multiple topics so posting here; will create bug ticket on GH as requested. I ran some import tests yesterday with a simple set of files: journal pages with one top-level block with properties and notes outlined below (see scrnsht from Logseq MD).
Quick notes - I have played with DB alpha version enough to understand the new tags (class-tags I'll call them) + how I envision using them. I have not played with the import feature til now.
First thing I noticed is that the import dialogue box is very non-intuitive; it's unclear what behavior to expect from each option. Clarity on this may need to come from both (1) improved dialogue box language and (2) accompanying migration documentation. I have only tested the 2 options mentioned below thus far, as those were most relevant to this set of journal notes (there are no #tags, #[[tags]] or [[tags]] in the notes; just properties).
Import additional tags from property values
From my testing, the dialogue box takes the name of a property (e.g. "event") and converts the property values (e.g. "course") to class-tags (e.g. #course)
The language here is confusing and the "e.g. type" did not help. Rough idea for improvement:
- Import these properties to convert their values to class-tags
- e.g. enter "event" to convert e.g. event:: meeting to the class-tag #meeting
Import tag parents from property values
I ran into UUID errors when attempting to import with property names in this field, so I have no idea what it's suppose to do. Possible bug?
Missing tags property
I ran several iterations to import the tags:: property and its values to no avail. This type of behavior is problematic and w/o warning. If "tags" property is uniquely problematic, I suggest adding new option to convert them to "Page Tags" or smth else on import.
Invalid blocks
No obvious issue with the blocks, but error occurs after some attempts to debug - removing properties, adding missing bullet to first block. Possible bug?
grave apex
viral lintel
