NotePlan / NotePlan/plugins

Dashboard bug: move to note is sometimes not removing items from the section properly

Open
#649 1 comment 0 reactions 1 assignee View on GitHub

@jgclark is already working on this.

Since Jul 1, 2025.

Dominant language
JavaScript
Stars
204
Forks
82
Avg merge
22h 27m
Merged PRs (30d)
3

Description

2025-07-01 16:28:31 | DEBUG | userInput / processChosenHeading :: headingLevel: 2 chosenHeading: 'kenna'
2025-07-01 16:28:31 | DEBUG | moveItemToRegularNote :: - Moving to note 'Family Todos Undated' under heading: 'kenna'
2025-07-01 16:28:31 | DEBUG | moveItemToRegularNote :: - newHeadingLevel: 2
2025-07-01 16:28:31 | DEBUG | coreAddTaskToNoteHeading :: starting for note 'Family Todos Undated' under heading 'kenna' text ! @kenna Sell the moped headingLevel 2
2025-07-01 16:28:31 | DEBUG | coreAddTaskToNoteHeading :: Adding task '! @kenna Sell the moped' to 'Family Todos Undated' below 'kenna'
2025-07-01 16:28:31 | DEBUG | NPP/findParaFromStringAndFilename :: starting with filename: 20250627.md, content: {! @kenna Sell the moped}
2025-07-01 16:28:31 | DEBUG | moveItemToRegularNote :: - Removing 1 para from original note 20250627.md
2025-07-01 16:28:31 | DEBUG | doMoveToNote :: - Sending remove line request for ID 13-6
2025-07-01 16:28:31 | DEBUG | bridgeClickDashboardItem :: ⏱️ ⚠️ 20,008ms for bridgeClickDashboardItem: "moveToNote" before processActionOnReturn()

  • numeric Setting 'newTaskSectionHeadingLevel' number: 2
  • numeric Setting 'maxItemsToShowInSection' number: 100
  • numeric Setting 'autoUpdateAfterIdleTime' number: 0
  • numeric Setting 'lookBackDaysForOverdue' number: 0
    2025-07-01 16:28:31 | DEBUG | getListOfEnabledSections :: sectionsToShow: OVERDUE,SEARCH
    2025-07-01 16:28:31 | DEBUG | processActionOnReturn :: TASK: updatedParagraph "N/A"
    2025-07-01 16:28:31 | DEBUG | processActionOnReturn :: REMOVE_LINE_FROM_JSON: for ID:13-6 task:{! @kenna Sell the moped}
    2025-07-01 16:28:31 | DEBUG | processActionOnReturn :: -> removing item 13-6 from sections[0].sectionItems[6]
    2025-07-01 16:28:31 | DEBUG | processActionOnReturn :: -> NOT asking for any further refresh: hopefully React will do its stuff!
    2025-07-01 16:28:31 | DEBUG | updateReactWindowFLC: handlerResult :: {
    "success": true,
    "actionsOnSuccess": [
    "REMOVE_LINE_FROM_JSON"
    ]
    }
    2025-07-01 16:28:31 | DEBUG | updateReactWindowFLC :: for item ID: 13-6 from OVERDUE to do REMOVE_LINE_FROM_JSON
    2025-07-01 16:28:31 ❗️ ERROR ❗️ updateReactWindowFLC :: no updatedParagraph param was given, and its not a Project update. So cannot update react window content for: ID=13-6. errorMsg=-
    2025-07-01 16:28:31 | DEBUG | - data.item at error: :: {
    "ID": "13-6",
    "itemType": "open",
    "teamspaceTitle": "",
    "para": {
    "noteType": "Calendar",
    "prefix": "* ",
    "dueDate": "2025-06-27",
    "rawContent": "* ! @kenna Sell the moped",
    "hasChild": false,
    "isAChild": false,
    "filename": "20250627.md",
    "lineIndex": 2,
    "title": "2025-06-27",
    "type": "open",
    "priority": 1,
    "indentLevel": 0,
    "isTeamspace": false,
    "startTime": "none",
    "changedDate": "2025-07-01T23:21:49.104Z",
    "content": "! @kenna Sell the moped"
    }
    }
    2025-07-01 16:28:31 | DEBUG | bridgeClickDashboardItem :: ⏱️ ⚠️ 20,052ms total runtime for bridgeClickDashboardItem: "moveToNote"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.