aboutsummaryrefslogtreecommitdiff
path: root/csharp/src/Google.Protobuf.Test/GeneratedMessageTest.cs
Commit message (Collapse)AuthorAgeFilesLines
* Compare floating point values bitwise in C#Jon Skeet2017-12-091-0/+11
| | | | | This is the manual code part of the Google.Protobuf library, and tests. Some tests will fail until codegen is changed and rerun.
* Regenerate all C# code and make it compileJon Skeet2016-04-201-16/+16
| | | | JSON tests fail, as we're not using OriginalNameAttribute yet.
* Replace StringBuilder with TextWriter in JsonFormatteravgweb2016-03-061-0/+9
|
* Validate that end-group tags match their corresponding start-group tagsJon Skeet2016-02-151-4/+3
| | | | | | | | This detects: - An end-group tag with the wrong field number (doesn't match the start-group field) - An end-group tag with no preceding start-group tag Fixes issue #688.
* Introduce ICustomDiagnosticMessage to allow for custom string formattingJon Skeet2016-01-131-0/+16
| | | | This fixes issue #933, effectively.
* Prohibit null values in map fieldsJon Skeet2016-01-111-1/+35
| | | | | On deserialization, missing values for message types are replaced with a "default" message.
* Include the oneof-case in equality and hash code generated code.Jon Skeet2015-10-241-0/+10
| | | | The included C# test will fail until the regenerated code is used, which is in the next commit.
* Address review comments.Jon Skeet2015-08-081-0/+22
|
* Validate that after reading a message, we've consumed as many bytes as we ↵Jon Skeet2015-08-051-8/+18
| | | | | | expected to. We should now have no conformance failures.
* Consume unknown fields when parsing.Jon Skeet2015-08-051-0/+29
| | | | | This is expected to be the cause of the conformance test failures. Generated code in next commit.
* Expose Coded*Stream constructors directly.Jon Skeet2015-08-031-5/+5
|
* Prohibit null values for string/bytes fields in generated code.Jon Skeet2015-07-301-0/+10
|
* remove the freeze APIJan Tattermusch2015-07-291-17/+0
|
* First pass at making field access simpler.Jon Skeet2015-07-221-160/+0
| | | | This is definitely not ready to ship - I'm "troubled" by the disconnect between a list of fields in declaration order, and a mapping of field accessors by field number/name. Discussion required, but I find that easier when we've got code to look at :)
* Revamp to reflection.Jon Skeet2015-07-211-23/+24
| | | | | | | | | | | | | | | | | Changes in brief: 1. Descriptor is now the entry point for all reflection. 2. IReflectedMessage has gone; there's now a Descriptor property in IMessage, which is explicitly implemented (due to the static property). 3. FieldAccessorTable has gone away 4. IFieldAccessor and OneofFieldAccessor still exist; we *could* put the functionality straight into FieldDescriptor and OneofDescriptor... I'm unsure about that. 5. There's a temporary property MessageDescriptor.FieldAccessorsByFieldNumber to make the test changes small - we probably want this to go away 6. Discovery for delegates is now via attributes applied to properties and the Clear method of a oneof I'm happy with 1-3. 4 I'm unsure about - feedback welcome. 5 will go away 6 I'm unsure about, both in design and implementation. Should we have a ProtobufMessageAttribute too? Should we find all the relevant attributes in MessageDescriptor and pass them down, to avoid an O(N^2) scenario? Generated code changes coming in the next commit.
* First pass at the big rename from ProtocolBuffers to Google.Protobuf.Jon Skeet2015-07-171-0/+760
We'll see what I've missed when CI fails...