aboutsummaryrefslogtreecommitdiffhomepage
path: root/csharp/src/Google.Protobuf/JsonParser.cs
Commit message (Collapse)AuthorAge
* Allow list values to be null when parsingGravatar Jon Skeet2018-03-01
|
* Add parser settings WithXyz methodsGravatar Jon Skeet2017-10-28
|
* Add JsonParser setting to ignore unknown field valuesGravatar Jon Skeet2017-10-28
| | | | | | | Note that the default behavior is still to throw an exception; you need to opt into ignoring unknown fields. Fixes #2838.
* Fixed parsing of BoolValue.Gravatar Jos Hickson2016-05-11
|
* Allow custom type URL prefixes in Any.PackGravatar Jon Skeet2016-04-29
| | | | | | (And likewise ignore the prefix in unpack.) Fixes issue #1459.
* Rename Preconditions to ProtoPreconditionsGravatar Jon Skeet2016-02-04
| | | | (Generated code changes in next commit.)
* Make sure thatGravatar Jon Skeet2016-01-15
| | | | | | "valueField": null is parsed appropriately, i.e. that it remembers that the field is set.
* Reject JSON containing the same oneof field twiceGravatar Jon Skeet2016-01-15
|
* Change handling of unknown enums: we now write out the value as a number.Gravatar Jon Skeet2016-01-15
|
* Extra strictness for FieldMask conversionGravatar Jon Skeet2016-01-15
|
* Fixes to JSON timestamp/duration representationsGravatar Jon Skeet2016-01-15
|
* Prohibit null values in repeated and map fields in JSONGravatar Jon Skeet2016-01-15
|
* Throw a better exception when invalid base64 is detected in JSONGravatar Jon Skeet2016-01-15
|
* Support (and test) numeric enum parsing in JSONGravatar Jon Skeet2016-01-15
|
* JSON conformance test fixesGravatar Jon Skeet2016-01-13
| | | | | - Spot an Any without a type URL - In the conformance test runner, catch exceptions due to generally-invalid JSON
* Improve number handling in JSON parsingGravatar Jon Skeet2016-01-06
| | | | | | - 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
* Handle JSON parsing for Any.Gravatar Jon Skeet2015-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...
* Tidy up reflection in advance of attempting to implement DynamicMessage.Gravatar Jon Skeet2015-11-22
| | | | | | | | | There are corner cases where MessageDescriptor.{ClrType,Parser} will return null, and these are now documented. However, normally they *should* be implemented, even for descriptors of for dynamic messages. Ditto FieldDescriptor.Accessor. We'll still need a fair amount of work to implement dynamic messages, but this change means that the public API will be remain intact. Additionally, this change starts making use of C# 6 features in the files that it touches. This is far from exhaustive, and later PRs will have more. Generated code changes coming in the next commit.
* Introduce a Parser property into MessageDescriptor, and populate it from ↵Gravatar Jon Skeet2015-11-19
| | | | | | generated types. Generated code coming in next commit - in a subsequent PR I want to do a bit of renaming and redocumenting around this, in anticipation of DynamicMessage.
* Generated code changes and manual changes for previous commit.Gravatar Jon Skeet2015-11-09
|
* Merge pull request #941 from jskeet/recursion-limitGravatar Jan Tattermusch2015-11-05
|\ | | | | Add recursion limit handling to JSON parsing.
| * Reimplement JSON recursion by detecting the depth in the tokenizer.Gravatar Jon Skeet2015-11-05
| | | | | | | | Added a TODO around a possible change to the tokenizer API, changing PushBack(token) into just Rewind() or something similar.
* | Merge pull request #940 from jskeet/json-namesGravatar Jon Skeet2015-11-05
|\ \ | | | | | | Move the creation of the "fields by JSON name" dictionary to the descriptor
* | | Created a new exception for JSON failures.Gravatar Jon Skeet2015-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.
| | * Add recursion limit handling to JSON parsing.Gravatar Jon Skeet2015-11-04
| |/ |/| | | | | Fixes issue #932.
| * Move the creation of the "fields by JSON name" dictionary to the descriptor.Gravatar Jon Skeet2015-11-04
|/
* Implement JSON parsing in C#.Gravatar Jon Skeet2015-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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-01 16:05:41 +0000