lnd.xprv/lnrpc/routerrpc
Daniel McNally f437b35fc6
lnrpc: set JS_STRING option for chan_id
This sets the `jstype` option to `JS_STRING` for all `chan_id` fields
in the proto rpc definition. `chan_id` is a 64 bit integer, which is
not natively supported by javascript's floating-point `number` with
only 52 bit precision. Nevertheless, by default protobuf will use the
`number` type for 64 bit integer fields in javascript, which can cause
loss of precision problems with `chan_id`. Explicitly setting the type
for javascript as a string will prevent these issues, and should not
interfere with its use as an identifier.
2019-10-14 14:53:54 -04:00
..
config_active.go routing: persist mission control data 2019-07-31 08:44:00 +02:00
config_default.go routing: persist mission control data 2019-07-31 08:44:00 +02:00
config.go routing: persist mission control data 2019-07-31 08:44:00 +02:00
driver.go lnrpc/routerrpc: add config, implement full RouterServer 2019-02-20 16:10:39 -08:00
log.go multi: remove dead code 2019-09-10 17:21:59 +02:00
router_backend_test.go lnrpc+lnrpc/routerrpc: add a new TLV record field to the Hop proto 2019-08-22 18:53:03 -07:00
router_backend.go multi: extend QueryRoutes RPC with CLTV limit field 2019-10-11 18:07:39 -04:00
router_server.go routing+routerrpc: take max cltv limit into account within path finding 2019-10-11 18:04:49 -04:00
router.pb.go lnrpc: set JS_STRING option for chan_id 2019-10-14 14:53:54 -04:00
router.proto lnrpc: set JS_STRING option for chan_id 2019-10-14 14:53:54 -04:00