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

Offen
#649 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@jgclark arbeitet bereits daran.

Seit 01.7.2025.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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"
Vorherrschende Sprache
JavaScript
Sterne
204
Forks
82
Ø Merge
22 Std. 27 Min.
Gemergte PRs (30 T.)
3

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus NotePlan/plugins

Alle Issues in NotePlan/plugins

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.