protobuf - Protocol Buffers – Google’s data interchange format

	Commit message (Collapse)	Author	Age
*	implement IComparable and comparison operators on Timestamp (#4318)	Warren Falk	2018-07-09
\|
*	Rename Preconditions to ProtoPreconditions	Jon Skeet	2016-02-04
\| \| \| \|	(Generated code changes in next commit.)
*	Ensure that FieldMask, Timestamp and Duration ToString() calls don't throw	Jon Skeet	2016-01-20
\| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Fixes to JSON timestamp/duration representations	Jon Skeet	2016-01-15
\|
*	Implement JSON parsing in C#.	Jon Skeet	2015-11-03
\| \| \| \| \| \| \| \| \| \|	This includes all the well-known types except Any. Some aspects are likely to require further work when the details of the JSON parsing expectations are hammered out in more detail. Some of these have "ignored" tests already. Note that the choice not to use Json.NET was made for two reasons: - Going from 0 dependencies to 1 dependency is a big hit, and there's not much benefit here - Json.NET parses more leniently than we'd want; accommodating that would be nearly as much work as writing the tokenizer This only really affects the JsonTokenizer, which could be replaced by Json.NET. The JsonParser code would be about the same length with Json.NET... but I wouldn't be as confident in it.
*	Document everything, and turn on errors if we fail to document anything in ↵	Jon Skeet	2015-08-04
\| \| \| \|	the future.
*	Format JSON for Duration and Timestamp.	Jon Skeet	2015-08-03
\| \| \| \|	This is taking an approach of putting all the logic in JsonFormatter. That's helpful in terms of concealing the details of whether or not to wrap the value in quotes, but it does lack flexibility. I don't think we want to allow user-defined formatting of messages, so that much shouldn't be a problem.
*	Well-known type operations for Timestamp and Duration (but not JSON formatting).	Jon Skeet	2015-07-31
	While I've provided operators, I haven't yet provided the method equivalents. It's not clear to me that they're actually a good idea, while we're really targeting C# developers who definitely can use the user-defined operators.