mirror of
https://github.com/libp2p/go-libp2p.git
synced 2025-09-26 20:21:26 +08:00
0fb7daca4a
* Add failing proto test * Add a new proto compilation script A proto file's *import path* is relative to one of the `--proto-path`s. Previously, the proto files were compiled separately. Some invocations used different values for the `--proto_path`, which led to inconsistent import paths in proto file descriptors. Typically, this wouldn't be a problem. However, if a downstream project uses `protoregistry.GlobalFiles` to inspect proto dependencies, it will fail to find a dependency's file descriptor when the dependency was compiled with a different `--proto_path`. By using a single script to generate all protobuf files, we can ensure the `--proto_path` is always set to the same sane value (the root of the project, as suggested in the [official documentation]). [official documentation]: https://protobuf.dev/programming-guides/proto2/#importing * Add go_package options so scripts/gen-proto.sh succeeds * Remove undesirable `go:generate protoc` directives * Run `go generate ./...` * Script uses arrays, I think we need bash --------- Co-authored-by: Marco Munizaga <git@marcopolo.io>
13 lines
248 B
Protocol Buffer
13 lines
248 B
Protocol Buffer
syntax = "proto2";
|
|
|
|
package plaintext.pb;
|
|
|
|
import "core/crypto/pb/crypto.proto";
|
|
|
|
option go_package = "github.com/libp2p/go-libp2p/core/sec/insecure/pb";
|
|
|
|
message Exchange {
|
|
optional bytes id = 1;
|
|
optional crypto.pb.PublicKey pubkey = 2;
|
|
}
|