You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jörg Hoh (Jira)" <ji...@apache.org> on 2020/06/21 12:26:00 UTC

[jira] [Commented] (SLING-8706) Injections for java.util.Optional<> should be automatic optional

    [ https://issues.apache.org/jira/browse/SLING-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141464#comment-17141464 ] 

Jörg Hoh commented on SLING-8706:
---------------------------------

[~sseifert], [~justin] ,[~kwin] : WDYT about the linked PR by [~etugarev]?

I would really love to have that feature available because it helps to make sling models more resilient against declared but unimplemented behavior.

> Injections for java.util.Optional<> should be automatic optional 
> -----------------------------------------------------------------
>
>                 Key: SLING-8706
>                 URL: https://issues.apache.org/jira/browse/SLING-8706
>             Project: Sling
>          Issue Type: Improvement
>          Components: Sling Models
>            Reporter: Jörg Hoh
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> The current approach to support optional injections requires to annotate the field with {{@Optional}} plus proper handling within the javacode (null checks etc), which can be forgotten.
> So instead of
> {code}
> @Inject @Optional
> String fieldname;
> {code}
> it should also be possible to use this
> {code}
> @Inject
> Optional<String> fieldname;
> {code}
> with the very same semantic. But the developer is forced to deal with the case that the value is not present.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)