protobuf - Protocol Buffers – Google’s data interchange format

	Commit message (Collapse)	Author	Age
*	Fix JsonTokenizer exception message	Jon Skeet	2017-11-29
\|
*	Add JsonParser setting to ignore unknown field values	Jon Skeet	2017-10-28
\| \| \| \| \| \| \|	Note that the default behavior is still to throw an exception; you need to opt into ignoring unknown fields. Fixes #2838.
*	Handle JSON parsing for Any.	Jon Skeet	2015-12-02
\| \| \| \|	This required a rework of the tokenizer to allow for a "replaying" tokenizer, basically in case the @type value comes after the data itself. This rework is nice in some ways (all the pushback and object depth logic in one place) but is a little fragile in terms of token push-back when using the replay tokenizer. It'll be fine for the scenario we need it for, but we should be careful...
*	Merge pull request #941 from jskeet/recursion-limit	Jan Tattermusch	2015-11-05
\|\ \| \| \| \|	Add recursion limit handling to JSON parsing.
\| *	Reimplement JSON recursion by detecting the depth in the tokenizer.	Jon Skeet	2015-11-05
\| \| \| \| \| \| \| \|	Added a TODO around a possible change to the tokenizer API, changing PushBack(token) into just Rewind() or something similar.
* \|	Created a new exception for JSON failures.	Jon Skeet	2015-11-05
\|/ \| \| \| \| \|	This is only thrown directly by JsonTokenizer, but surfaces from JsonParser as well. I've added doc comments to hopefully make everything clear. The exception is actually thrown by the reader within JsonTokenizer, in anticipation of keeping track of the location within the document, but that change is not within this PR.
*	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.