Fix Delete Deserialization Error #33
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_rpc!33
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_fix_delete_deserialization_error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Generated SDK
_deletemethods calledrpc_call::<String>, but the dispatch layer auto-parses a handler's stringified bool ("true"/"false") back into a JSON bool on the wire.Clients hit
invalid type: boolean true, expected a string at line 1 column 30on every successful delete — the row got removed server-side, but the UI showed an error.switch generator output to
rpc_call::<serde_json::Value>for_deletedelete discards the value anyway, and
Valueaccepts whichever JSON shape the dispatch produces.Scope
crates/generator/src/rust/rust_client.rs:208.lhumina_code/hero_osis.Related Issues
Generated SDK delete methods called rpc_call::<String>, but the dispatch layer auto-parses a handler's stringified bool ("true"/"false") back into a JSON bool on the wire. Result: clients hit "invalid type: boolean true, expected a string at line 1 column 30" on every successful delete. Switch to rpc_call::<serde_json::Value> — delete discards the value anyway, and Value accepts whichever JSON shape the dispatch produces. Refs: lhumina_code/hero_os#49 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>fix(generator): use serde_json::Value for delete RPC return typeto Fix Delete Deserialization Errorfatmaebrahim referenced this pull request2026-04-27 11:01:20 +00:00
e93edac5d398bfb767fc