- 26 Jul, 2017 1 commit
-
-
Thomas Van Lenten authored
-
- 25 Jul, 2017 1 commit
-
-
Jisi Liu authored
-
- 05 Jul, 2017 1 commit
-
-
Yilun Chong authored
-
- 28 Feb, 2017 1 commit
-
-
Jie Luo authored
There might be duplicated enum values when allow_alias is true. Add PreferredAlias into OriginalNameAttribute to remove the duplication (#2727)
-
- 27 Jan, 2017 1 commit
-
-
Jie Luo authored
-
- 19 Jan, 2017 1 commit
-
-
Jon Skeet authored
This consists of: - Changing the codegen for the fixed set of options protos, to parse unknown fields instead of skipping them - Add a new CustomOptions type in the C# support library - Expose CustomOptions properties from the immutable proto wrappers in the support library Only single-value options are currently supported, and fetching options values requires getting the type right and knowing the field number. Both of these can be addressed at a later time. Fixes #2143, at least as a first pass.
-
- 12 Dec, 2016 1 commit
-
-
Jan Tattermusch authored
-
- 03 Dec, 2016 1 commit
-
-
Joshua Haberman authored
* 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.
-
- 04 Jul, 2016 1 commit
-
-
Jon Skeet authored
-
- 20 Apr, 2016 1 commit
-
-
Jon Skeet authored
JSON tests fail, as we're not using OriginalNameAttribute yet.
-
- 18 Mar, 2016 1 commit
-
-
alien authored
Conflicts: csharp/src/Google.Protobuf/JsonFormatter.cs
-
- 04 Feb, 2016 2 commits
- 15 Jan, 2016 1 commit
-
-
Jon Skeet authored
"valueField": null is parsed appropriately, i.e. that it remembers that the field is set.
-
- 13 Jan, 2016 1 commit
-
-
Jon Skeet authored
This fixes issue #933, effectively.
-
- 11 Jan, 2016 1 commit
-
-
Jon Skeet authored
On deserialization, missing values for message types are replaced with a "default" message.
-
- 15 Dec, 2015 1 commit
-
-
Jon Skeet authored
-
- 22 Nov, 2015 1 commit
-
-
Jon Skeet authored
Generated code changes for previous commit (basically InternalBuildGeneratedFileFrom => FromGeneratedCode)
-
- 19 Nov, 2015 1 commit
-
-
Jon Skeet authored
-
- 09 Nov, 2015 1 commit
-
-
Jon Skeet authored
-
- 24 Oct, 2015 1 commit
-
-
Jon Skeet authored
-
- 01 Oct, 2015 1 commit
-
-
Jon Skeet authored
-
- 30 Sep, 2015 1 commit
-
-
Jon Skeet authored
-
- 29 Sep, 2015 2 commits
- 01 Sep, 2015 1 commit
-
-
Jon Skeet authored
Other changes are due to the well-known types changing without us regenerating.
-
- 06 Aug, 2015 1 commit
-
-
Jon Skeet authored
-
- 05 Aug, 2015 2 commits
- 31 Jul, 2015 2 commits
- 30 Jul, 2015 3 commits
-
-
Jon Skeet authored
-
Jon Skeet authored
-
Jan Tattermusch authored
-
- 22 Jul, 2015 2 commits
- 21 Jul, 2015 1 commit
-
-
Jon Skeet authored
-
- 17 Jul, 2015 1 commit
-
-
Jon Skeet authored
We'll see what I've missed when CI fails...
-