elgonzo

> Json.NET's default behavior swaps from opt-out to opt-in if certain attributes like [DataContract] are present. It has to use opt-in for [DataContract]/[DataMember], because that is the specified and documented...

> especially when acting like a tool while doing so Acting like a tool? My, my, making friends must come quite natural to you... :grin:

FYI: duplicate of https://github.com/JamesNK/Newtonsoft.Json/issues/1318

Please check the documentation at https://www.newtonsoft.com/json/help/html/ConvertingJSONandXML.htm, which (among other things) specifically mentions and addresses how serialization of arrays in such situations can be enforced.

It depends. Start with trying to use the classes offered in Newtonsoft.Json.Linq (JArray, JObject, JValue, etc..), and read your json data into such a JArray/JObject/JValue representation. This can then be...

This is not a bug in Json.NET, but a bug in your project. Before i explain what happens on a technical level in your code there, i want to point...

It's 2022 now and I don't know why you still don't have heard about such basic things like [XPath queries](https://www.w3schools.com/xml/xpath_syntax.asp). :kissing_heart: HAP has a function for XPath queries: https://html-agility-pack.net/select-nodes XPath...

> some of **your** well-known competing products In case it got missed what i wrote at the end of my last comment: I am not representing the HAP project. I...

> Then this issue becomes to add the documentation … True.

I strongly disagree with keeping the current behavior. Here is why: HtmlAttributeCollection is able and does maintain multiple attributes of the same name. Iterating over the HtmlAttributeCollection will yield all...