fix(backend): delete child notes when their parent note is deleted (fix #134)

[Pratyush-Panda-2006]

Description

This pull request prevents child notes from being orphaned in the database when a parent note or stack container is deleted. Previously, when deleteNote was invoked, the parent note was deleted via findOneAndDelete but its child notes (associated via parentId) remained in MongoDB, bloating the database with unreachable records.

Changes

• Updated the deleteNote controller in backend/src/controllers/notesController.js to execute Note.deleteMany({ parentId: id, userId: req.user._id }) after the parent note is successfully deleted.

Fixes #134

Summary by CodeRabbit

• Bug Fixes

  • Deleting a note now also removes any associated child notes owned by the same user, preventing leftover notes from appearing after a parent note is removed.

• Documentation

  • Added a new reference document listing high-priority product and platform issues, including suggested fixes and issue links.

[coderabbitai]

Warning

Review limit reached

@Pratyush-Panda-2006, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ee9707ff-4715-4c76-9278-d815dc71f853

📥 Commits

Reviewing files that changed from the base of the PR and between 34cf8ac and 5229feb.

⛔ Files ignored due to path filters (1)

• backend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• backend/package.json
• backend/src/controllers/notesController.js
• backend/src/middleware/rateLimiter.js
• backend/src/routes/notesRoutes.js
• backend/src/server.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}