[
https://issues.apache.org/jira/browse/DAFFODIL-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olabusayo Kilo resolved DAFFODIL-3019.
--------------------------------------
Resolution: Fixed
Fixed in c780dba7335fa77d7a53bddc56ec56c0a73b5b18
> Remove java.util.Optional's from new API
> ----------------------------------------
>
> Key: DAFFODIL-3019
> URL: https://issues.apache.org/jira/browse/DAFFODIL-3019
> Project: Daffodil
> Issue Type: Bug
> Components: API
> Affects Versions: 4.0.0
> Reporter: Steve Lawrence
> Assignee: Olabusayo Kilo
> Priority: Major
> Fix For: 4.0.0
>
>
> The new API has a number of functions that have "Optional" parameters. But it
> sounds like normal Java convention is to not have "Optional" parameters but
> to instead just allow null to indicate optionality.
> Since our API is Java-first, we should remove Optionals and ensure we have
> functions that allow null to be be passed. And update our Scala code to
> handle null values, possibly wrapping the argument in an Option so that
> internally we follow normal scala conventions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
