Hey! Thanks for the feedback!
Yes, indeed. Here’s my take on it:
JSON to XML : this allows to use the already existing XPath nodes to query JSON but has some drawbacks such as
- not accepting properties starting with numbers (which are valid in JSON but not XML)
- not allowing structures without root element.
- when constructing JSON from XElement nodes, it would serialize a spread of one value as a single property and only start serializing as array if count > 1, which does not work with some APIs that expect arrays, even for one value
- it converts everything to string no matter what when serializing, which also does not work when interacting with APIs that explicitly want integers for instance (see Create an xml element that has int32 values)
NewtonSoft vs System.Text.Json : no particular opinion there, I thought it’d make more sense to go with the default/built-in microsoft thing and found the node set to be quite easy to use when parsing JSON. Never really tried serializing to JSON or building JSON on the fly though.
Yes, definitely :-)
And yes, that! Also encountered that today with a custom datatype from a C# solution.