[
https://issues.apache.org/jira/browse/WICKET-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-6412.
-------------------------------------
Resolution: Fixed
Assignee: Martin Grigorov (was: Sven Meier)
Fix Version/s: 8.0.0-M7
I've updated the javadoc with these possible usages.
With this API one can use #orElse() both for Wicket's needs and for the
application's ones.
If #orElse() returns T then only the application may make use of it, and this
is sub-optimal.
> Model#orElse behavior is inconsistent!
> --------------------------------------
>
> Key: WICKET-6412
> URL: https://issues.apache.org/jira/browse/WICKET-6412
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 8.0.0-M6
> Reporter: Jarosław
> Assignee: Martin Grigorov
> Fix For: 8.0.0-M7
>
>
> Dear Wicket Devs,
> I was very confused by Model#orElse method.
> Model and Optional have similar methods and these methods behave the same:
> {code}
> Optional<Integer> _optional = Optional.ofNullable("1").map(Integer::parseInt);
> IModel<Integer> _model = Model.of("1").map(Integer::parseInt);
> {code}
> Unfortunately "orElse" behavior is totally confusing!
> {code}
> Integer integer = _optional.orElse(0);
> IModel<Integer> integerIModel = _model.orElse(0); //WRONG!
> {code}
> It should return a Model's Object instead of Model itself!
> This definitely break the least surprise rule, so can you please change that
> before Wicket8 final release?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
