Viewing/Editing summary.md deletes all my files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.2k
- Forks
- 1.9k
- PR merge metrics
- PR metrics pending
Description
Problem
When I at, first set up my book, I updated summary.md and it made the pages for me. Later, I sometimes did that, sometimes made the page and then made a choice about whether to include it. (I don't know if that is relevant) But regardless, I'm at a point where I need to add new pages and when I click on summary.md in VSCode and open the file, even if I don't edit it, it marks all of my pages as uncommited and deletes the content.
Steps
- Click on summary.md and open it in VS Code
- Make any change
- All files are deleted
Possible Solution(s)
No response
Notes
It's possible that this is only an issue if running: mdbook serve --open but I'm not sure and I'm scared to go back and try this. I'm in the middle of the semester trying to use this as a way to provide a course reference / workbook and I don't want to lose anything else. The first time it happened, it deleted all the MD files I have made under src that were impacted by me reordering summary.md and created new files that only had the title. It deleted my versions with all my work, even though most of those, perhaps all of those files were originally created by adding to summary.md in the first place. Please help.
Version
mdbook v0.4.21
Contributor guide
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
Start by reproducing the report with mdBook v0.4.21 using mdbook serve --open, then inspect summary.md and the affected Markdown files under src. Compare the files before and after opening or changing summary.md; done means existing page content is preserved while pages are reordered or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100