Get desktop application:
View/edit binary Protocol Buffers messages
This is a test service
(message has no fields)
(message has no fields)
This is a test method
Test that RPC services work.
(message has no fields)
(message has no fields)
Leading enum comment
Zero value comment
This is a leading comment
Leading field comment
Trailing field comment
Leading nested enum comment
Zero value comment
Leading nested message comment
Leading nested message field comment
(message has no fields)
(message has no fields)
Used in: , , ,
Define these after TestAllTypes to make sure the compiler can handle that.
Used in: , , ,
Test int32, uint32, int64, uint64, and bool are all compatible
Used in: ,
Previously, message containing enum called Type cannot be used as value of map field.
Previously, message cannot contain map field called "entry".
This proto includes a recursively nested message.
Test String and Bytes: string is for valid UTF-8 strings
This proto includes every type of field in both singular and repeated forms.
Used in: , ,
Singular
Defined in unittest_import_public.proto
Repeated
Defined in unittest_import_public.proto
For oneof test
Used in:
Intentionally negative.
Used in: ,
The field name "b" fails to compile in proto1 because it conflicts with a local variable named "b" in one of the generated methods. Doh. This file needs to compile in proto1 to test backwards-compatibility.
Test message with CamelCase field names. This violates Protocol Buffer standard style.
*/ <- This should not close the generated doc comment
(message has no fields)
Test an enum that has multiple values with the same number.
Used in:
We list fields out of order, to ensure that we're using field number and not field index to determine serialization order.
Used in:
The field name "b" fails to compile in proto1 because it conflicts with a local variable named "b" in one of the generated methods. Doh. This file needs to compile in proto1 to test backwards-compatibility.
Test that we can use NestedMessage from outside TestAllTypes.
Tests maps.
Used in:
Test that mutual recursion works.
Used in:
Used in:
Test oneofs.
Test that really large tag numbers don't break anything.
The largest possible tag number is 2^28 - 1, since the wire format uses three bits to communicate wire type.
Parsing repeated fixed size values used to fail. This message needs to be used in order to get a tag of the right size; all of the repeated fields in TestAllTypes didn't trigger the check.
Check for a varint type, just for good measure.
These have two-byte tags.
Three byte tags.
(message has no fields)
Two map fields share the same entry default instance.
Test an enum with large, unordered values.
Used in:
In proto3, value 0 must be the first one specified SPARSE_F = 0;
A message with the same fields as TestPackedTypes, but without packing. Used to test packed <-> unpacked wire compatibility.