You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I've been implementing on a fork a bunch of file operations for the REST API (I've built an MCP over it). Before I start to submit PRs by PRs, I'd like to check that some choices I made are ok:
For file rename for example, I chose to use the existing PATCH endpoint with special headers:
PATCH /vault/folder/old-file.md
Content-Type: text/plain
Operation: replace
Target-Type: file
Target: name
Is overloading PATCH with Target-Type: file the right approach, or should we have dedicated endpoints like POST /vault/{path}/rename (which I struggled to parse simply) ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
I've been implementing on a fork a bunch of file operations for the REST API (I've built an MCP over it). Before I start to submit PRs by PRs, I'd like to check that some choices I made are ok:
For file rename for example, I chose to use the existing PATCH endpoint with special headers:
PATCH /vault/folder/old-file.md
Content-Type: text/plain
Operation: replace
Target-Type: file
Target: name
Is overloading PATCH with Target-Type: file the right approach, or should we have dedicated endpoints like POST /vault/{path}/rename (which I struggled to parse simply) ?
Beta Was this translation helpful? Give feedback.
All reactions