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
feat(api-contract): nodeControl.getBalance schemas and contract definition [1/4] (#739)
* feat(api-contract): nodeControl.getBalance schemas and contract definition [1/4]
Add GetBalanceResultSchema and the standalone getBalanceContract on
contracts/node-control. Deliberately leave the `nodeControl` router
unwired until the SDK handler ships in the implementation PR.
The SDK core's `implement(nodeControl).router({...})` is exhaustive, so
adding to `nodeControl` here without the matching handler in
@moneydevkit/core would break the workspace build. Splitting the
wire-up into the next commit keeps each PR independently green.
Bump api-contract to 0.1.27.
* fix(api-contract): re-export GetBalanceResult{,Schema} from package root
Address Codex review on #739: the node-control GetBalanceResult type
and schema were declared but not re-exported, so external consumers
couldn't import them via @moneydevkit/api-contract.
Aliased to NodeGetBalanceResult{,Schema} to avoid colliding with the
checkout-side GetBalanceResult{,Schema} that ships in PR [2/4]
(#740), mirroring the existing NodeProgrammaticPayoutInput alias.
The standalone getBalanceContract itself is intentionally NOT
re-exported: none of its node-control siblings (payoutContract,
programmaticPayoutContract, invoiceCreateBolt11Contract, ...) are
re-exported either. Consumers access the contract through the
nodeControl namespace once PR [3/4] wires it in.
0 commit comments