Web UI 'save note' fails 422 — JS sends {query, markdown} but backend expects {filename, content}

[dolilod]

Repro

Tested on enzyme v0.5.3 (macos-arm64).

1. enzyme serve -p <vault> (any vault)
2. Open http://127.0.0.1:8765/ in browser
3. Use the UI's note-save feature → fails with HTTP 422

Root cause

Frontend/backend payload mismatch.

JS bundle (/assets/index-C3fkMwYV.js) sends:

fetch(`${baseURL}/notes/save`, {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ query: S, markdown: c })
})

Rust backend (/notes/save route) expects:

{ "filename": "<path>", "content": "<markdown body>" }

Server response on the JS-shaped payload:

HTTP 422 Unprocessable Entity
Failed to deserialize the JSON body into the target type: missing field `filename`

Confirmed working when manually shaped correctly

curl -X POST http://127.0.0.1:8765/notes/save \
  -H "Content-Type: application/json" \
  -d '{"filename":"00-Inbox/test.md","content":"# Test"}'
# → HTTP 200, {"file_path":"...","relative_path":"...","success":true}
# → file actually created in vault

So the backend save logic is fine. Just the frontend asset sends wrong field names.

Fix (one-line in JS source pre-bundle)

- body: JSON.stringify({ query: S, markdown: c })
+ body: JSON.stringify({ filename: S, content: c })

Or update the backend to accept both field names for backward compat.

Reference

JS source location (from binary string): crates/enzyme-api/src/explore_pipeline.rs references /notes/save route. The frontend that ships with the binary is at /assets/index-C3fkMwYV.js.

[jshph]

Hey! Haven't touched this bit of code in a bit but glad to hear you might be finding some use of out of it. Mind if I ask what your use case is or if you're just exploring?

…

On Mon, Apr 27, 2026 at 11:00 AM dolilod ***@***.***> wrote: *dolilod* created an issue (jshph/enzyme#7) <#7> Repro Tested on *enzyme v0.5.3* (macos-arm64). 1. enzyme serve -p <vault> (any vault) 2. Open http://127.0.0.1:8765/ in browser 3. Use the UI's note-save feature → fails with HTTP 422 Root cause *Frontend/backend payload mismatch.* JS bundle (/assets/index-C3fkMwYV.js) sends: fetch(`${baseURL}/notes/save`, { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ query: S, markdown: c })}) Rust backend (/notes/save route) expects: { "filename": "<path>", "content": "<markdown body>" } Server response on the JS-shaped payload: HTTP 422 Unprocessable Entity Failed to deserialize the JSON body into the target type: missing field `filename` Confirmed working when manually shaped correctly curl -X POST http://127.0.0.1:8765/notes/save \ -H "Content-Type: application/json" \ -d '{"filename":"00-Inbox/test.md","content":"# Test"}'# → HTTP 200, {"file_path":"...","relative_path":"...","success":true}# → file actually created in vault So the backend save logic is fine. Just the frontend asset sends wrong field names. Fix (one-line in JS source pre-bundle) - body: JSON.stringify({ query: S, markdown: c })+ body: JSON.stringify({ filename: S, content: c }) Or update the backend to accept both field names for backward compat. Reference JS source location (from binary string): crates/enzyme-api/src/explore_pipeline.rs references /notes/save route. The frontend that ships with the binary is at /assets/index-C3fkMwYV.js. — Reply to this email directly, view it on GitHub <#7>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQKP4RVVCOZMABIKKVTRFL4X5YW7AVCNFSM6AAAAACYIBKUX6VHI2DSMVQWIX3LMV43ASLTON2WKOZUGMZTMNZRHEYDGMQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>