aboutsummaryrefslogtreecommitdiff
path: root/csharp/src/Google.Protobuf.Test
Commit message (Collapse)AuthorAgeFilesLines
* Give C# ByteString a sensible GetHashCode implementation.Jon Skeet2016-12-161-0/+13
| | | | Fixes #2511.
* remove leading whitespace in C# xml commentsJan Tattermusch2016-12-125-84/+84
|
* Factored Conformance and Benchmark test messages into shared test schema. ↵Joshua Haberman2016-12-032-1/+3691
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#1971) * Factored Conformance test messages into shared test schema. * Updated benchmarks to use new proto3 message locations. * Fixed include path. * Conformance: fixed include of Python test messages. * Make maven in Rakefile use --batch-mode. * Revert changes to benchmarks. On second thought I think a separate schema for CPU benchmarking makes sense. * Try regenerating C# protos for new test protos. * Removed benchmark messages from test proto. * Added Jon Skeet's fixes for C#. * Removed duplicate/old test messages C# file. * C# fixes for test schema move. * Fixed C# to use the correct TestAllTypes message. * Fixes for Objective C test schema move. * Added missing EXTRA_DIST file.
* Fix csharp/src/Google.Protobuf.Test/project.jsonJulien Brianceau2016-11-141-1/+1
| | | | | | | This change fixes the following Chromium presubmit error: third_party/protobuf/csharp/src/Google.Protobuf.Test/project.json could not be parsed: Expecting property name: line 25 column 3 (char 482)
* Change JSON field name formattingJon Skeet2016-11-031-6/+6
| | | | | | | | | This affects cases with leading capital letters. This breaks compatibility with previous C# releases, but fixes compatibility with other implementations. See #2278 for details.
* Bring C#'s ToPascalCase method in line with C++.Jon Skeet2016-07-271-0/+6
| | | | | (This still doesn't fix the conformance tests, but at least we're now consistent with the C++ code.)
* Move to dotnet cli for building, and .NET Core (netstandard1.0) as target ↵Jon Skeet2016-07-149-178/+68
| | | | | | | platform (#1727) Move to dotnet cli for building, and .NET Core (netstandard1.0) as target platform This also updates the version number to 3.0.0-beta4
* Implement RepeatedField.AddRange (#1733)Jon Skeet2016-07-131-2/+88
| | | | | | | | | | | | | | | | | | | * Improve exception throwing implementation in collections * Implement RepeatedField.AddRange. This fixes issue #1730. * Optimize AddRange for sequences implementing ICollection (Also fix a few more C# 6-isms.) * Remove the overload for Add(RepeatedField<T>) We now just perform the optimization within AddRange itself. This is a breaking change in terms of "drop in the DLL", but is source compatible, which should be fine.
* Remove unnecessary reflection callJon Skeet2016-07-081-19/+2
| | | | | This is the only call to TypeExtensions.IsValueType, so we can remove that method, making the whole type conditionally compiled out for .NET 3.5
* Changes to generated code from previous commitJon Skeet2016-07-046-78/+1107
|
* Adding conditional compiler symbol to support .NET 3.5 (#1713)detlevschwabe2016-06-281-1/+2
| | | | * Adding condition compiler symbol to support .NET 3.5
* Expose JsonFormatter.WriteValue.Jon Skeet2016-06-231-0/+47
| | | | | This isn't useful to most users, but can be handy in advanced use cases, as requested in #1465.
* Move test for standalone BoolValue to JsonParserTestJon Skeet2016-05-113-7/+19
| | | | | | Also added a standalone formatter test, for confidence. Have validated that undoing the change in 835fb947 breaks the tests (i.e. we are still testing that the change is required).
* Fixed parsing of BoolValue.Jos Hickson2016-05-111-0/+7
|
* Allow custom type URL prefixes in Any.PackJon Skeet2016-04-293-0/+47
| | | | | | (And likewise ignore the prefix in unpack.) Fixes issue #1459.
* Regenerate all C# code and make it compileJon Skeet2016-04-2012-113/+113
| | | | JSON tests fail, as we're not using OriginalNameAttribute yet.
* Remove duplicate test cases.Jon Skeet2016-04-012-2/+0
| | | | (NCrunch noticed these.)
* Code review fixesalien2016-03-291-0/+1
|
* csharp: add support for the json_name optionalien2016-03-182-5/+186
| | | | | Conflicts: csharp/src/Google.Protobuf/JsonFormatter.cs
* Replace StringBuilder with TextWriter in JsonFormatteravgweb2016-03-061-0/+9
|
* Fix copy/paste typo in CodedInputStreamTestJon Skeet2016-03-011-1/+1
|
* Implement IDisposable for CodedInputStream and CodedOutputStreamJon Skeet2016-02-292-0/+50
| | | | | This fixes issue #679 and issue #1282. (The .gitignore change is just around ncrunch; I can put it in a separate PR if you really want.)
* Merge pull request #1240 from jskeet/validate_groupJan Tattermusch2016-02-182-6/+51
|\ | | | | Validate that end-group tags match their corresponding start-group tags
| * Validate that end-group tags match their corresponding start-group tagsJon Skeet2016-02-152-6/+51
| | | | | | | | | | | | | | | | 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.
* | Add more tests around merging wrappersJon Skeet2016-02-151-2/+41
|/ | | | This was in an attempt to fix the wrapper handling corner case, but it's really fiddly.
* Use checked-in key to build ReleaseSignedJan Tattermusch2016-02-091-1/+1
|
* Generated code changes from previous commitJon Skeet2016-02-042-14/+14
|
* Generated code for GeneratedCodeInfo changeJon Skeet2016-02-046-59/+59
|
* Merge pull request #1158 from jskeet/nonnormalized-tostringJan Tattermusch2016-01-265-2/+94
|\ | | | | Ensure that FieldMask, Timestamp and Duration ToString() calls don't throw
| * Ensure that FieldMask, Timestamp and Duration ToString() calls don't throwJon Skeet2016-01-205-2/+94
| | | | | | | | | | | | | | | | | | | | | | | | | | The usage of ICustomDiagnosticMessage here is non-essential - ToDiagnosticString doesn't actually get called by ToString() in this case, due to JsonFormatter code. It was intended to make it clearer that it *did* have a custom format... but then arguably I should do the same for Value, Struct, Any etc. Moving some of the code out of JsonFormatter and into Duration/Timestamp/FieldMask likewise feels somewhat nice, somewhat nasty... basically there are JSON-specific bits of formatting, but also domain-specific bits of computation. <sigh> Thoughts welcome.
* | Fix mistakes in highest-representable float64 integersJon Skeet2016-01-211-2/+2
|/
* Merge pull request #1096 from jskeet/custom-to-stringJan Tattermusch2016-01-194-1/+63
|\ | | | | Introduce ICustomDiagnosticMessage to allow for custom string formatting
| * Introduce ICustomDiagnosticMessage to allow for custom string formattingJon Skeet2016-01-134-1/+63
| | | | | | | | This fixes issue #933, effectively.
* | Fix broken testJon Skeet2016-01-151-1/+1
| |
* | Make sure thatJon Skeet2016-01-152-4/+51
| | | | | | | | | | | | "valueField": null is parsed appropriately, i.e. that it remembers that the field is set.
* | Reject JSON containing the same oneof field twiceJon Skeet2016-01-151-0/+7
| |
* | Change handling of unknown enums: we now write out the value as a number.Jon Skeet2016-01-152-16/+13
| |
* | Extra strictness for FieldMask conversionJon Skeet2016-01-152-0/+18
| |
* | Allow the original field name (rather than camel-cased) when parsing JSONJon Skeet2016-01-151-0/+8
| |
* | Fixes to JSON timestamp/duration representationsJon Skeet2016-01-154-9/+73
| |
* | Prohibit null values in repeated and map fields in JSONJon Skeet2016-01-151-0/+30
| |
* | Throw a better exception when invalid base64 is detected in JSONJon Skeet2016-01-151-0/+9
| |
* | Support (and test) numeric enum parsing in JSONJon Skeet2016-01-151-0/+20
| |
* | Fix handling of repeated wrappersJon Skeet2016-01-151-0/+24
| | | | | | | | | | Previously we were incorrectly packing wrapper types. This also refactors FieldCodec a bit as well, using more C# 6-ness.
* | JSON conformance test fixesJon Skeet2016-01-131-0/+7
|/ | | | | - Spot an Any without a type URL - In the conformance test runner, catch exceptions due to generally-invalid JSON
* Prohibit null values in map fieldsJon Skeet2016-01-115-77/+51
| | | | | On deserialization, missing values for message types are replaced with a "default" message.
* Merge pull request #1098 from jskeet/wkt-jsonJan Tattermusch2016-01-082-25/+41
|\ | | | | Ensure all formatted well-known-type values are valid JSON
| * Ensure all formatted well-known-type values are valid JSONJon Skeet2016-01-062-25/+41
| | | | | | | | | | | | | | This involves quoting timestamp/duration/field-mask values, even when they're not in fields. It's better for consistency. Fixes issue #1097.
* | Improve number handling in JSON parsingJon Skeet2016-01-061-12/+35
|/ | | | | | - Tighten up on Infinity/NaN handling in terms of whitespace handling (and test casing) - Validate that values are genuinely integers when they've been parsed from a JSON number (ignoring the fact that 1.0000000000000000001 == 1 as a double...) - Allow exponents and decimal points in string representations
* Generated code changes from previous commit.Jon Skeet2015-12-156-58/+58
|