[
https://issues.apache.org/jira/browse/DAFFODIL-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2231.
-----------------------------------
Verified the specified commit (commit fc660df1aecfce81f276b79b9c9f9eb9ce893153)
is included in the latest pull from the daffodil repository.
Verified, via review, change identified in the commit comment were implemented.
Rolled back commit to a pre-fix commit and verified that it still created the
leading separator.
Verified that with the fix-commit the leading separator is no longer added in
the unparse result.
Verified the affected daffodil subproject sbt test suites executed successfully
including the added tests.
> Separator unparsed even when dfdl:occursCount expression is zero
> ----------------------------------------------------------------
>
> Key: DAFFODIL-2231
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2231
> Project: Daffodil
> Issue Type: Bug
> Components: Unparsing
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 3.5.0
>
>
> See the attached schema, and the following data
> {quote}
> Year,Make,Model,Description,Price
> 1997,Ford,E350,"ac, abs, moon",2999.99
> 1999,Chevy,Venture Extended Edition,,4900.00
> 1999,Chevy,Venture Extended Edition,Very Large,5000.00
> 1996,Jeep,Grand Cherokee,"MUST SELL! air, moon roof, loaded",4799.00
> {quote}
> If the 'header' variable is set to "none" then this schema correctly does not
> create a <header> element because occursCount evaluates to 0. However, on
> unparse even though there is no header element, Daffodil still creates a
> separator, causing an empty newline to be output as the first line.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
