96029f3c4a
json_decode automatically convert numeric string to integer, so that we need to convert it back. However, this will suceed to parse invalid json data with string field set as integer even though it should have failed. Because, the failure case is less often than the succeeding case, we decided to make this change. Users should make sure their data don't use integer for string fields by themselves.
23 lines
1.2 KiB
Plaintext
23 lines
1.2 KiB
Plaintext
Recommended.FieldMaskNumbersDontRoundTrip.JsonOutput
|
|
Recommended.FieldMaskPathsDontRoundTrip.JsonOutput
|
|
Recommended.FieldMaskTooManyUnderscore.JsonOutput
|
|
Recommended.Proto3.JsonInput.BytesFieldBase64Url.JsonOutput
|
|
Recommended.Proto3.JsonInput.BytesFieldBase64Url.ProtobufOutput
|
|
Recommended.Proto3.JsonInput.DurationHas3FractionalDigits.Validator
|
|
Recommended.Proto3.JsonInput.DurationHas6FractionalDigits.Validator
|
|
Recommended.Proto3.JsonInput.DurationHas9FractionalDigits.Validator
|
|
Recommended.Proto3.JsonInput.DurationHasZeroFractionalDigit.Validator
|
|
Recommended.Proto3.JsonInput.FieldMaskInvalidCharacter
|
|
Required.Proto3.JsonInput.FloatFieldTooLarge
|
|
Required.Proto3.JsonInput.FloatFieldTooSmall
|
|
Required.Proto3.JsonInput.DoubleFieldTooSmall
|
|
Required.Proto3.JsonInput.Int32FieldNotInteger
|
|
Required.Proto3.JsonInput.Int64FieldNotInteger
|
|
Required.Proto3.JsonInput.RepeatedFieldWrongElementTypeExpectingStringsGotInt
|
|
Required.Proto3.JsonInput.StringFieldNotAString
|
|
Required.Proto3.JsonInput.Uint32FieldNotInteger
|
|
Required.Proto3.JsonInput.Uint64FieldNotInteger
|
|
Required.Proto3.JsonInput.Int32FieldLeadingSpace
|
|
Required.Proto3.JsonInput.OneofFieldDuplicate
|
|
Required.Proto3.ProtobufInput.ValidDataRepeated.FLOAT.JsonOutput
|