First crack at single-page imports

phildenhoff commented 1 year ago

This is the first step towards #38 — it adds a single-page import process similar to how Omnivore works.

Users can use this ONLY IF they enable both "Sync to a single page?" and "Enable broken, experimental features".
Users can choose whether to import all Raindrops created since the last sync, or only those with highlights.
Users can change the page Raindrops are imported to ("Page Name for Single Page Imports")

There is no attempt at upserting at the moment — if a Raindrop has been updated after the sync time, it's re-inserted.

I think, at the moment, everything is appended to the bottom. We probably don't want that. There's also no formatting, nor are user's default tags setting respected.

There's tons of clean up / code reorganization to do. Having one giant "importHighlightsSinceLastSync" function gives me no joy, but it does sort of work!

Here's a demo: note that the plugin does not redirect to the page by default.

https://github.com/phildenhoff/logseq-raindrop/assets/17505728/bc1ee3d8-967c-4cf6-9f08-39dcca1d1125

phildenhoff commented 1 year ago

Current dependencies on/for this PR:

main
- PR #50 👈
- PR #60
  - PR #61

This comment was auto-generated by Graphite.

phildenhoff commented 1 year ago

@phildenhoff started a stack merge that includes this pull request via Graphite.

phildenhoff commented 1 year ago

@phildenhoff merged this pull request with Graphite.

phildenhoff / logseq-raindrop

First crack at single-page imports #50