package unittest_issues

Get desktop application:
View/edit binary Protocol Buffers messages

Used in: DeprecatedFieldsMessage

(message has no fields)

Used in: DeprecatedFieldsMessage

• DEPRECATED_ZERO = 0

• one = 1

• int32 PrimitiveValue = 1

• repeated int32 PrimitiveArray = 2

• optional DeprecatedChild MessageValue = 3

• repeated DeprecatedChild MessageArray = 4

• DeprecatedEnum EnumValue = 5

• repeated DeprecatedEnum EnumArray = 6

Issue 307: when generating doubly-nested types, any references should be of the form A.Types.B.Types.C.

(message has no fields)

(message has no fields)

(message has no fields)

Issue 45: http://code.google.com/p/protobuf-csharp-port/issues/detail?id=45

• int32 item = 1

Used in: NegativeEnumMessage

• NEGATIVE_ENUM_ZERO = 0

• FiveBelow = -5

• MinusOne = -1

• NegativeEnum value = 1

• repeated NegativeEnum values = 2

• repeated NegativeEnum packed_values = 3

• int32 types = 1

• int32 descriptor = 2

Force a nested type called Types

(message has no fields)

These fields are deliberately not declared in numeric order, and the oneof fields aren't contiguous either. This allows for reasonably robust tests of JSON output ordering. TestFieldOrderings in unittest_proto3.proto is similar, but doesn't include oneofs. TODO: Consider adding oneofs to TestFieldOrderings, although that will require fixing other tests in multiple platforms. Alternatively, consider just adding this to unittest_proto3.proto if multiple platforms want it.

• int32 plain_int32 = 4

• oneof o1

  • string o1_string = 2

  • int32 o1_int32 = 5

• string plain_string = 1

• oneof o2

  • int32 o2_int32 = 6

  • string o2_string = 3

• string name = 1

  Message for testing the effects for of the json_name option

• string description = 2

• string guid = 3