sawhney17 / logseq-smartblocks

MIT License
172 stars 12 forks source link

Random block refs invalidated after re-index #11

Closed ksqsf closed 2 years ago

ksqsf commented 2 years ago

In the latest version (0.6.2) of logseq, after doing a full re-index, the references of random blocks created by Smart Blocks become invalid.

My use case is a simple one: it picks a random block with a certain tag. (The same as this video.)

After creating the block ref, I can jump to it via the ref, so the ID is correct. But after re-index, the ID changes. I don't know if this is a bug of Logseq, or a bug of Smart Blocks (forgetting to make the ID persist by adding it to the text file), or it is a change in logseq that Smart Blocks hasn't caught up with.

ksqsf commented 2 years ago

I should add that the block referenced has not been referenced before. So it's quite likely that Smart Blocks forgot to make the ID persist?

sawhney17 commented 2 years ago

Yeah, that's likely the issue. I'll fix the issue today.

sawhney17 commented 2 years ago

Should be fixed in the latest release