protobuf

18743 Commits

204 Branches

369 Tags

184 MiB

Tag: Branch: Tree: b51d59e193

Commit Graph

Author	SHA1	Message	Date
Protobuf Team Bot	4834eb75cb	Move some :unittest_(cpp\|upb)_rust_proto target to be colocated with the .proto file that defines them This CL doesn't unbreak the bazel tests, but is yak shaving in prep for changes that will. This makes it more straightforward how the tests are broken by having bazel test rules name rust proto library targets that don't exist in bazel repo, instead of naming targets that do exist but are bogus. Also correct unittest_edition target to match the order of words in the .proto file name (edition_unittest) PiperOrigin-RevId: 674295376	7 months ago
Protobuf Team Bot	5d341470da	Initial pass of a proto_eq gtest macro. This version works where both sides are the same message, messageview or messagemut type, but not any mix of them (e.g. cannot compare a message against its corresponding view). PiperOrigin-RevId: 671091099	7 months ago

Author

SHA1

Message

Date

Protobuf Team Bot

4834eb75cb

Move some :unittest_(cpp|upb)_rust_proto target to be colocated with the .proto file that defines them

This CL doesn't unbreak the bazel tests, but is yak shaving in prep for changes that will. This makes it more straightforward how the tests are broken by having bazel test rules name rust proto library targets that don't exist in bazel repo, instead of naming targets that do exist but are bogus.

Also correct unittest_edition target to match the order of words in the .proto file name (edition_unittest)

PiperOrigin-RevId: 674295376

7 months ago

Protobuf Team Bot

5d341470da

Initial pass of a proto_eq gtest macro.

This version works where both sides are the same message, messageview or messagemut type, but not any mix of them (e.g. cannot compare a message against its corresponding view).

PiperOrigin-RevId: 671091099

7 months ago

2 Commits (b51d59e193d4301d7e102ef0509787e7a89519f1)