feat: Add file rename functionality via PATCH /vault/{filepath}

[duquesnay]

Summary

adds file rename functionality to the Obsidian Local REST API

API Usage

Rename a file using PATCH with these headers:

curl -X PATCH https://localhost:27124/vault/path/to/file.md \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Operation: replace" \
  -H "Target-Type: file" \
  -H "Target: name" \
  -d "new-filename.md"

Implementation Details

• API Endpoint: PATCH /vault/{filepath}
• Headers Required:
  • Operation: replace (legacy compatibility)
  • Target-Type: file
  • Target: name
• Request Body: New filename
• Link Preservation: Uses app.fileManager.renameFile() to update internal vault references
• Error Handling: Returns 404 for missing files, 409 for conflicts, 400 for validation errors

Commit Structure

This PR contains 5 commits extracted from git history:

1. 3221a95 - fix: Add null check for Target header in PATCH requests
2. 7bd91d8 - fix: improve error messages for PATCH operations
3. 77eac7a - feat: Add file rename endpoint with PATCH /vault/{filepath}
4. 4636d36 - test: Add tests for file rename operation
5. b7702b3 - docs: Add OpenAPI documentation for file rename operation

Testing

Includes tests for:

• Successful rename operation
• Error handling for non-existent files
• Conflict detection when destination exists
• FileManager API integration via mocks

Files Modified

• src/requestHandler.ts - Core implementation and fixes
• src/requestHandler.test.ts - Test coverage
• src/constants.ts - Error message improvements
• docs/openapi.yaml - API documentation
• docs/src/lib/patch.jsonnet - Documentation templates

[duquesnay]

Context: commits extracted from my personal fork
Thank you for any feedback as I'm trying to break down into granular commits and PRs a series of features originally done in a not-so-clean series of commits (file crud, directory crud, tags crud, links, advanced search).
I've been using these in an MCP client