diff options
| author | Oskari Timperi <oskari.timperi@iki.fi> | 2018-04-29 10:42:42 +0300 |
|---|---|---|
| committer | Oskari Timperi <oskari.timperi@iki.fi> | 2018-04-29 10:42:51 +0300 |
| commit | 666f08193be545fab8b14e0e15fd9913e3a2b38b (patch) | |
| tree | 2d46a71a00e39b8b6c3e706556bb26e8ff7224d7 /examples/simple | |
| parent | d2925ec9864ecfa349ec2bc34706396814df34ce (diff) | |
| download | nimpb-666f08193be545fab8b14e0e15fd9913e3a2b38b.tar.gz nimpb-666f08193be545fab8b14e0e15fd9913e3a2b38b.zip | |
Try to be more in line with proto3 spec
And the other implementations. Namely, use the default values of fields for
checking if they are present. This means that we also don't generate the
`hasSomeField` procs for anything else than oneofs and messages.
Also make some changes to oneofs. Include a `NotSet` in the oneof enums which
can be used to see if a oneof field has a value or not.
With these changes, the conformance test suite reports the following:
Required.Proto3.JsonInput.Any.JsonOutput
Required.Proto3.JsonInput.Any.ProtobufOutput
Required.Proto3.JsonInput.AnyNested.JsonOutput
Required.Proto3.JsonInput.AnyNested.ProtobufOutput
Required.Proto3.JsonInput.AnyUnorderedTypeTag.JsonOutput
Required.Proto3.JsonInput.AnyUnorderedTypeTag.ProtobufOutput
Required.Proto3.JsonInput.AnyWithDuration.JsonOutput
Required.Proto3.JsonInput.AnyWithDuration.ProtobufOutput
Required.Proto3.JsonInput.AnyWithFieldMask.JsonOutput
Required.Proto3.JsonInput.AnyWithFieldMask.ProtobufOutput
Required.Proto3.JsonInput.AnyWithInt32ValueWrapper.JsonOutput
Required.Proto3.JsonInput.AnyWithInt32ValueWrapper.ProtobufOutput
Required.Proto3.JsonInput.AnyWithStruct.JsonOutput
Required.Proto3.JsonInput.AnyWithStruct.ProtobufOutput
Required.Proto3.JsonInput.AnyWithTimestamp.JsonOutput
Required.Proto3.JsonInput.AnyWithTimestamp.ProtobufOutput
Required.Proto3.JsonInput.AnyWithValueForInteger.JsonOutput
Required.Proto3.JsonInput.AnyWithValueForInteger.ProtobufOutput
Required.Proto3.JsonInput.AnyWithValueForJsonObject.JsonOutput
Required.Proto3.JsonInput.AnyWithValueForJsonObject.ProtobufOutput
Required.Proto3.JsonInput.Int32FieldLeadingZero
Required.Proto3.JsonInput.Int32FieldNegativeWithLeadingZero
Required.Proto3.JsonInput.Struct.ProtobufOutput
Required.Proto3.JsonInput.Uint64FieldMaxValueNotQuoted.JsonOutput
Required.Proto3.JsonInput.Uint64FieldMaxValueNotQuoted.ProtobufOutput
Required.Proto3.JsonInput.ValueAcceptNull.JsonOutput
Required.Proto3.JsonInput.ValueAcceptNull.ProtobufOutput
Required.Proto3.ProtobufInput.RepeatedScalarSelectsLast.DOUBLE.JsonOutput
Required.Proto3.ProtobufInput.ValidDataRepeated.DOUBLE.JsonOutput
CONFORMANCE SUITE FAILED: 574 successes, 194 skipped, 0 expected failures,
29 unexpected failures.
Diffstat (limited to 'examples/simple')
0 files changed, 0 insertions, 0 deletions