search

sawhney17 / logseq-pdf-export

MIT License
107 stars 6 forks source link

Error: ... is not a valid UUID string for [text](((UUID))) #49

Closed Red-Skuller closed 5 months ago

Red-Skuller commented 6 months ago

I can only print with retained formatting. If i try templates it throws this error:

Uncaught (in promise) Error: (65899250-e022-4b46-96e9-b8e030e2dabe is not a valid UUID string. at $logseq$sdk$utils$uuid_or_throw_error$$ (main.js:94653:9) at br.$logseq$api$block$get_block$$ (main.js:94716:427) at br.R (lsplugin.core.js:2:49447) at br. (lsplugin.core.js:2:93271) at a.emit (lsplugin.core.js:2:28521) at X. (lsplugin.core.js:2:88623) at lsplugin.core.js:2:53506 at Array.forEach () at X.listener (lsplugin.core.js:2:53491)

It seems it doesn't support this style of links text) Screenshot_20231230_130939 Screenshot_20231230_131012

sdasda7777 commented 5 months ago

Same here, this bug is bizarre :/

image

sdasda7777 commented 5 months ago

@Red-Skuller, could you clarify what the expected behaviour is?

Red-Skuller commented 5 months ago

It should export [text](((UUID))) as text or as a link to the UUID named text

sdasda7777 commented 5 months ago

With my fix, it seems to export [text](((UUID))) as just text with no link, is that okay?

image

image

Strangely enough, [text]((UUID)) exports to [text]Header at given UUID. I'm not completely sure how this feature was envisioned to work 🤔

Red-Skuller commented 5 months ago

Yes. That's plenty. Thank you!

sdasda7777 commented 5 months ago

Great, no problem 😄 But to be honest I'm not sure how soon is one of the maintainers (@sawhney17 or @kumaresh0) likely to review it 😅