Avoid null in return values about aws-sdk-java-v2 HOT 4 CLOSED

The other complication for having Optional on our pojo's based on service models is that (currently) it's considered backwards compatible from a service API perspective to 'relax' the validation on a "required" field. This would result in compile-time backwards incompatibility. See lengthy discussion here aws/aws-sdk-java#965

One possibility is that for Pojo's we could annotate them with meta-data from the service model. This would be subject to change as the service model does but it might be a good indicator.

I agree for classes that we control returning Optional as opposed to null is desirable. I'd like to go further and annotate our methods with @Nonnull (or similar) when we know that we're not going to return null. This will aid interoperability with languages like Kotlin.

from aws-sdk-java-v2.

It might be tricky to standardize the throws-exception vs returns-null between services for existing APIs because we federate that out to the service owners, but returning Optional<Response> instead of null for services that do so for not-found results makes a lot of sense. Good catch.

from aws-sdk-java-v2.

Partly related is #529, so service responses will not return null Lists (and Maps in the future) unless customized to do so.

from aws-sdk-java-v2.

We're doing the best we can to fulfill this feature request as we build new features.

from aws-sdk-java-v2.