fix: proxy_list_refs calls node endpoint directly instead of xrpc client The panproto-xrpc NodeClient.list_refs() calls dev.panproto.node.listRefs but the cospan node registers the handler at dev.cospan.node.listRefs. Use proxy_get_json to call the node's actual registered endpoint.

Author: Aaron Steven White
Commit c209a76787953010ce0364018ef9ffbcdd335900
Parent: 13a2124869
Structural diff unavailable

These commits were pushed via plain git push, so no pre-parsed schemas are available. Install git-remote-cospan and re-push via panproto:// to see scope-level changes, breaking change detection, and semantic diffs.

brew install panproto/tap/git-remote-cospan
1 file changed +10 -10
@@ -51,16 +51,16 @@ pub async fn proxy_list_refs(
5151     State(state): State<Arc<AppState>>,
5252     Query(params): Query<RepoParams>,
5353 ) -> Result<Json<serde_json::Value>, AppError> {
54-    let refs = node_proxy::list_refs(&state, &params.did, &params.repo)
55-        .await
56-        .map_err(AppError::NotFound)?;
57-
58-    let refs_json: Vec<serde_json::Value> = refs
59-        .into_iter()
60-        .map(|(name, id)| serde_json::json!({ "ref": name, "target": id.to_string() }))
61-        .collect();
62-
63-    Ok(Json(serde_json::json!({ "refs": refs_json })))
54+    let result = node_proxy::proxy_get_json(
55+        &state,
56+        &params.did,
57+        &params.repo,
58+        "dev.cospan.node.listRefs",
59+        &[],
60+    )
61+    .await
62+    .map_err(AppError::Upstream)?;
63+    Ok(Json(result))
6464 }
6565 
6666 /// GET /xrpc/dev.cospan.node.proxy.getHead
cospan · schematic version control on atproto built on AT Protocol