mirror of
https://github.com/lightninglabs/loop.git
synced 2026-08-13 12:33:03 +02:00
dad103530f
Protobuf does not allow naming conflicts for files within the same process, because all proto messages register themselves in a global registry. This is problematic because the server's itests import the client's looprpc package to make rpc queries to the loopd client, thus importing duplicate common.proto and server.proto from the client's looprc package (since they're both in there as well). This change moves the server's proto files into their own directory so that they are not imported when we want to use the client's files. We cannot change the package name for the server, because that would be a breaking change (the package name is included in URIS). Fortunately, we have the go_package option which allows us to place generated files in a different location. |
||
|---|---|---|
| .. | ||
| codec.go | ||
| codec_test.go | ||
| interface.go | ||
| log.go | ||
| loop.go | ||
| loopin.go | ||
| loopout.go | ||
| meta.go | ||
| migration_01_costs.go | ||
| migration_02_swap_publication_deadline.go | ||
| migration_03_last_hop.go | ||
| migration_04_updates.go | ||
| migration_04_updates_test.go | ||
| protocol_version.go | ||
| protocol_version_test.go | ||
| raw_db_test.go | ||
| store.go | ||
| store_test.go | ||
| swapstate.go | ||