🐛(backend) hide restore action for inherited deletion

[ydnd]

Purpose

Fix #2127.

When a parent document is soft-deleted, child documents inherit the deleted state through ancestors_deleted_at. However, child documents still exposed the restore ability even when the child document itself was not directly deleted.

This could make the frontend show a restore action for a child document that cannot be restored independently.

Proposal

• Expose the restore ability only when the document itself has deleted_at set.
• Add a backend test covering the case where only an ancestor document is deleted.

External contributions

General requirements

• I have read and followed the contributing guidelines
• I have read and agreed to the Code of Conduct
• I have added corresponding tests for new features or bug fixes (if applicable)

Skip the checkbox below 👇 if you're fixing an issue or adding documentation

• Before submitting a PR for a new feature I made sure to contact the product manager

CI requirements

• I made sure that all existing tests are passing
• I have signed off my commits with git commit --signoff (DCO compliance)
• I have signed my commits with my SSH or GPG key (git commit -S)
• My commit messages follow the required format: <gitmoji>(type) title description
• I have added a changelog entry under ## [Unreleased] section (if noticeable change)

AI requirements

• I used AI assistance to produce part or all of this contribution
• I have read, reviewed, understood and can explain the code I am submitting
• I can jump in a call or a chat to explain my work to a maintainer

[coderabbitai]

Walkthrough

In Document.get_abilities, the condition for the restore ability is tightened to require both that the user is the owner and that deleted_at is non-null on the document itself. Previously, ownership alone was sufficient. A new test case is added that creates a document with a soft-deleted parent, fetches the child document's detail endpoint as the owner, and asserts that abilities.restore is False.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the core fix: preventing restore actions from appearing for child documents when only ancestors are deleted, directly addressing the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description clearly explains the bug being fixed: child documents incorrectly expose a restore ability when only an ancestor is deleted, not the document itself.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 and usage tips.}