You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, some codebases continue to utilize the Optional<List> style. However, it is clearer to simply use an empty collection to signify that a parameter is absent. Since version 4.3, the Spring framework has offered the ObjectProvider, which is effective for managing the optionality of injection points. Conveniently, Armeria also leverages ObjectProvider.
(e.g. ArmeriaSpringActuatorAutoConfiguration.java)
Suggestion
Replace Optional<List<T>> parameter to ObjectProvider<T>
The text was updated successfully, but these errors were encountered:
#5573)
Motivation:
Optional<T> is not as compatible as ObjectProvider<T>, which is included
in Spring Framework since Spring 4.3, so use ObjectProvider would
improve the programmatic resolution of Beans.
Modifications:
Two file are affected, AbstractArmeriaAutoConfiguration.java and
ArmeriaReactiveWebServerFactoryAutoConfiguration.java
Result:
Closes#5527 .
Motivation
Currently, some codebases continue to utilize the Optional<List> style. However, it is clearer to simply use an empty collection to signify that a parameter is absent. Since version 4.3, the Spring framework has offered the ObjectProvider, which is effective for managing the optionality of injection points. Conveniently, Armeria also leverages ObjectProvider.
(e.g.
ArmeriaSpringActuatorAutoConfiguration.java
)Suggestion
Replace
Optional<List<T>>
parameter toObjectProvider<T>
The text was updated successfully, but these errors were encountered: