Christer van der Meeren

Hi! Just wondering if it would be possible to implement this soon-ish (say, during the coming week or two)? I need to decide whether to work around this, but the...

I'd like this, too. I need to differentiate between null and missing values. (For example, in [JSON:API](http://jsonapi.org/), if a PATCH request has a property set to `null`, it means "set...

Just to be clear, are you saying that with System.Text.Json it's not possible at all to get correct paths when implementing JSON converters for objects? (Except perhaps a hacky solution...

I have noticed that it's possible at least get the correct line number and byte position. In terms of the code in this repo, instead of calling `Deserialize` here: https://github.com/Tarmil/FSharp.SystemTextJson/blob/479c38162ffe51751b2aba1300b3531ea3d32f3f/src/FSharp.SystemTextJson/Record.fs#L87...

Actually, the `LineNumber` and `BytePositionInLine` properties of the `JsonException` are still incorrect, but at least the message is correct.

To be clear, if I currently have two identically named fields (in different parts of the hierarchy) that both use query conventions, then fetching the schema fails with: > The...

Ideally, there'd be a global option to automatically name the field similar to `MutationConventionOptions.PayloadTypeNamePattern`, which would allow me to set something like `"{TypeName}{FieldName}Result"`. (I would argue that should be the...

To be clear, I experience this as a problem due to the schema snapshot test I have. Reading the diff when updating the snapshot is much more difficult than it...

I did not delete it, but since it was off-topic, I reported it as such after several days of inactivity had passed. My intention was for the owners of this...

There may be many issues related to default enum values. Yours clearly seems to be a completely separate issue for the following reasons, as I described in my (now deleted)...