Ralf Sternberg

Sorry, I can't understand your question. What is the _input_ you have and what is the _output_ you expect?

``` java new JsonObject() .add("userId", user.getUserId()) .add("userName", user.getUserName()) .add("password", user.getPassword()) .toString(); ```

It is intentional and should remain the default, because the JSON spec does not allow for single quotes. However, I plan on implementing a parser configuration that would allow for...

Hi @haruntuncay, I'm not actively maintaining this project and won't have time to review contributions, sorry.

Actually, considering objects with the same set of members but a different order as _not equal_ was a conscious decision. I see `JsonObject` and `JsonArray` more as a representations of...

@mafagafogigante right, we should add JavaDoc for `JsonObject#equals()`. Currently, it inherits from `Object#equals`. Good point! As for the performance, I don't think it's a problem if the new `equalsIgnoreOrder()` is...

@awvalenti we don't use `HashMap` for performance reasons. Our implementation is faster, especially for small objects, has a smaller memory footprint, and does not create wrapper objects for every element,...

@mafagafogigante I'm not generally opposed to the idea of a `toMap()` method, but I see your concerns. In particular, I wonder how much value a `Map` would provide beyond the...

> In my opinion, toMap would only be useful if recursive. I think I agree on that. In fact, calling `equals()` on the returned map would in turn call the...

If I understand correctly, your suggestion is to add methods like `getInt(String)`, `getBoolean(String)`, etc. to `JsonObject`. These methods would return a "default fallback value" if the object does not contain...