noteplan_edit_content.edit_line doesn't seem to honor the dryRun flag

Open Beginner friendly
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
api

Research direction

Start by locating the TypeScript handler for the noteplan_edit_content tool and its edit_line action, then trace how the dryRun argument is handled. Reproduce the request with MCP inspector against the scratch note. Done means dryRun: true reports the operation without changing the note content.

Written by the indexing model from the issue text.

Description

Using MCP inspector, on a scratch note called scratch, I ran:

{
  "method": "tools/call",
  "params": {
    "name": "noteplan_edit_content",
    "arguments": {
      "action": "edit_line",
      "title": "scratch",
      "content": "* Spike test task ^spk1a2 EDITED",
      "line": 3,
      "dryRun": true
    },
    "_meta": {
      "progressToken": 3
    }
  }
}

...then looked at the note in NotePlan and found that it was actually updated with the new text. I'd, of course, expect the content to not change when using dryRun: true.

Dominant language
TypeScript
Stars
16
Forks
4
No merged PRs in 30d

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.

More from NotePlan/noteplan-mcp

All issues in NotePlan/noteplan-mcp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.