[
https://issues.apache.org/jira/browse/DAFFODIL-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2843.
-----------------------------------
Verified the specified commit (commit fab8bf5d20b26a56912ab2a736a2bf5275f5a36a)
is included in the latest pull from the daffodil repository.
Verified, via review, changes identified in the commit comment were
implemented.
Verified the affected daffodil subproject sbt test suites executed
successfully, including additional tests.
Verified the nightly test suite executes successfully with no unexpected
failures.
> Unclear how to create Parse/UnparseError from ParseOrUnparseState
> -----------------------------------------------------------------
>
> Key: DAFFODIL-2843
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2843
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 3.5.0
> Reporter: Olabusayo Kilo
> Assignee: Mike Beckerle
> Priority: Major
> Fix For: 3.8.0
>
>
> It is unclear how to create a parse/unparse error using ParseOrUnparseState
> while creating a layer transform. Currently we can create a SDE using
> ParseOrUnparseState, but there are situations where the issue is with the
> data, not the schema.
> A possible workaround is to manually recreate what PE and UE do as in:
> {code:scala}
> parserOrUnparseState match {
> case pstate: PState => // do what PE(...) does
> case ustate: UState => // do what UE(...) does
> }
> {code}
> Related to DAFFODIL-2841
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
