AuroraMiddleware/protobuf
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
400d3888b9
protobuf/conformance/failure_list_php.txt

21 lines
1.0 KiB
Plaintext
Raw Normal View History

Add conformance test for php (#2655)
2017-02-01 20:47:58 +00:00
Recommended.FieldMaskNumbersDontRoundTrip.JsonOutput
Recommended.FieldMaskPathsDontRoundTrip.JsonOutput
Recommended.FieldMaskTooManyUnderscore.JsonOutput
Fix conformance tests
2017-07-25 21:37:37 +00:00
Recommended.Proto3.JsonInput.BytesFieldBase64Url.JsonOutput
Recommended.Proto3.JsonInput.BytesFieldBase64Url.ProtobufOutput
Fix php well known type conformance tests (#3828) * Fix php well known type conformance tests * Properly generate code for test.proto * Provide GPBMetadata files in c extensions for generated files to import. * Remove unnecessary test * Clean up code * Add declaration for initOnce. * Refactoring
2017-11-03 19:30:09 +00:00
Recommended.Proto3.JsonInput.FieldMaskInvalidCharacter
Merge from master
2017-07-25 18:52:33 +00:00
Required.Proto3.JsonInput.FloatFieldTooLarge
Required.Proto3.JsonInput.FloatFieldTooSmall
Required.Proto3.JsonInput.DoubleFieldTooSmall
Required.Proto3.JsonInput.Int32FieldNotInteger
Required.Proto3.JsonInput.Int64FieldNotInteger
Convert integer to string if field is string field in json 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.
2019-01-28 08:51:45 +00:00
Required.Proto3.JsonInput.RepeatedFieldWrongElementTypeExpectingStringsGotInt
Parse nested listvalue in json for ruby (#5867) * Add conformance test for nested listvalue * Fix upb for parsing repeated Value/ListValue * Add failed repeated ListValue conformance test into php failure list
2019-03-12 17:56:58 +00:00
Required.Proto3.JsonInput.RepeatedListValue.JsonOutput
Required.Proto3.JsonInput.RepeatedListValue.ProtobufOutput
Convert integer to string if field is string field in json 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.
2019-01-28 08:51:45 +00:00
Required.Proto3.JsonInput.StringFieldNotAString
Merge from master
2017-07-25 18:52:33 +00:00
Required.Proto3.JsonInput.Uint32FieldNotInteger
Required.Proto3.JsonInput.Uint64FieldNotInteger
Required.Proto3.JsonInput.Int32FieldLeadingSpace
Required.Proto3.JsonInput.OneofFieldDuplicate
Required.Proto3.ProtobufInput.ValidDataRepeated.FLOAT.JsonOutput
Reference in New Issue Copy Permalink