Potential Dataloss: Deleting an entry from the property page's node table has no confirmation dialog
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- frontend
Research direction
Find the component that renders the property page's node table, likely in a frontend directory. Look for the delete action handler and compare it to other delete actions in the app that show a confirmation dialog. Add a confirmation step before the deletion call. Test by reproducing the bug steps to ensure the dialog appears.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
On a property page, the table listing all nodes that have this property allows deleting an entry. This deletion happens immediately, without any confirmation dialog. This is inconsistent with other delete actions in the app, which ask for confirmation, and can lead to unintended data loss.
Reproduce the Bug
- Open a property page showing the table of all nodes that have this property set.
- Trigger the delete action on one of the entries in that table.
- The entry is deleted immediately — no confirmation dialog appears.
Expected Behavior
Deleting an entry from the property page's node table should show a confirmation dialog, consistent with other destructive delete actions in the app.
Screenshots
https://github.com/user-attachments/assets/efd61776-47dd-4ea6-8734-7cafa42f3082
Files
No response
Browser, Desktop or Mobile Platform Information
- Platform: Linux Desktop
- Version: 2.0.1-alpha+nightly.20260923
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!)
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from logseq/db-test
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Table filter "does not contain" is case-sensitive while "contains" is notPossibly taken @tiensonqin claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Sorting a tag table by a checkbox gives the same order ascending and descendingPossibly taken @tiensonqin claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Disabling Flashcards in Settings does not disable Flashcard shortcuts or tagsPossibly taken @tiensonqin claimed this 17 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Similar issues
-
Table: Space fires onActivate in single-selection mode — the reference doc and the JSDoc disagreeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sidorares/react-x11-components#764 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jspreadsheet/ce#1809 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
backnotprop/plannotator#1840 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug: directory index route root priority is overwritten when wildcard is falsePossibly taken @TalhaHunter101 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fastify/fastify-static#617 ·