Open cjfagerstrom opened 10 months ago
phildenhoff
commented
10 months ago Good catch! (And thank you for reporting these bugs — it's very much appreciated)
I'm not sure this is an easy fix. As far as I know, it's not really supported within Logseq's properties system.
That said, to get around it, you don't need to include the notes as a property (and it logically doesn't make a ton of sense to). You can add the notes variable below the properties block.
cjfagerstrom
commented
10 months ago I assumed it was likely an issue with logseq and needing to escape characters (I also noticed that markdown in raindrop notes does not work - at least not in the properties field, which was expected). I don't often use the notes in raindrop, but I might want to leave myself something there. I honestly would rather have the notes added as an h3/h4 level nested block as notes aren't really a "property". More of an attachment.
phildenhoff
commented
10 months ago You might be able to do that by tweaking the import template. I think if you add two new lines or a dash (-) that Logseq automatically turns it into another nested bullet? The Logseq API isn't the best, so providing easy controls for that in the plugin would be a challenge
When there is a line break in notes in raindrop and the notes are added in the middle of the other fields (url/tags/date created) any text on subsequent lines is not included in the properties field. New lines are included as separate new line notes outside the properties.
