UX: Show progress for Markdown Mirror full regeneration
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Search first
- I searched and no similar issues were found
What Happened?
Doing a Markdown Mirror full regeneration for this graph took 11:21 minutes to complete. Users don't get any feedback how far it is completed, if it still does anything and how long it will take.
OG Import "notes-logseq imported at 2026-05-27": {:entities 23292, :pages 5103, :blocks 18176, :classes 19, :properties 120, :objects 5629, :property-pairs 3152, :datoms 189316} (34.4MB DB)
Reproduce the Bug
- Run Markdown Mirror full regeneration on a big graph
Expected Behavior
Show progress like import for any longer running task like this.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
NixOS 25.11.10684.8fd9daa3db09
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260624
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the Markdown Mirror full regeneration entry point and comparing it with the existing import progress behavior. Done means a large full regeneration visibly reports progress and ongoing status, including for the described graph.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100