Ivan “CLOVIS” Canet
Ivan “CLOVIS” Canet
And in the case where you actually want to know if the object contains the literal `null`, you could still use `json.get("test").isNull()` so no feature is lost.
This would make working with this API a lot easier, please at least consider it.
There is currently a problem with `org.codehaus.mojo.signature:java15:1.0` that dislikes every reference to any Optional object; stacktrace: `JsonObject.java:595: Undefined reference: java.util.Optional java.util.Optional.ofNullable(Object)` A line alike this one appears for each use...
That's probably why, but Travis is not having it, probably because of some dependency. I'm not knowledgeable in any way in the Travis ecosystem, so I don't think I will...
I'm really busy right now, at most I'll be able to do it in ~week. Also, it would be nice to add @NotNull and @Nullable annotations to improve Kotlin compatibility:...
What I meant, is the others methods than plain simple `Optional#get`, like: - `Optional#ifPresent(lambda-expression)` - `Optional#flatMap(lambda-expression)` - `Optional#orElse(value)` (the equivalent of the current system with default values) - `Optional#orElseGet(lambda-expression)` -...
That would mean adding methods like `getOptional`, `getOptionalInt` etc, right?
Mostly, with some differences for primitives because they cannot be null.
I was thinking about the second version.
Also, because the methods `getInt` always have 2 parameters (name & default value), we could simply do something like: `int getInt(String name, int default);` `OptionalInt getInt(String name);` This way, both...