André Willik Valenti

"data-type" seems nice! I read some texts about adding custom attributes to HTML elements and I started using them on my framework project (on a different context). Using data-\* is...

I agree with you. If data-type has higher precedence, the interface will surely be consistent enough :). I thought about the type="date" thing you mentioned. The Date type exists only...

Here's a simple test case for the scenario described: `assertEquals(Json.parse("{\"a\":1,\"b\":2}"), Json.parse("{\"b\":2,\"a\":1}"));`

Hello, I see now that it was a conscious decision, especially after I found a test case specifically stating that. I don't quite agree that JsonObject and Array should represent...

Clone of Jackson? I've used Jackson a little and had problems with it, but why would these features lead minimal-json to becoming a copy of Jackson? And what's your opinion...

The question is: > An equalsIgnoreOrder() would work. However, test output would be something like "expected true, found false" - not very informative. > > Another possible solution would be...

You got me convinced that minimal-json should in fact be minimal :). However, `equalsIgnoreOrder()` also follows the direction of non-minimal approach, although on a lesser degree than `toMap()`. My opinion...

Oops, O(1) was a typo, indeed. Sorry! I see your point about performance and agree with it. I haven't understand this part: "ask everyone to write ordering-independant equality checks". Which...

Wait a second... I thought the map to be used would be a generic `Map`. But it's not: JsonObject keys are always Strings. The map would be `Map`. String's hashCode,...

This "duplicate key" thing is a bit scary :)... I was thinking about it yesterday. I thought the JSON spec prohibited it, but it simply says nothing about it, leaving...