[
https://issues.apache.org/jira/browse/DAFFODIL-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885164#comment-17885164
]
Steve Lawrence commented on DAFFODIL-2810:
------------------------------------------
I think escalating all warnings is probably enough. The use case of this is we
want to fail on unexpected warnings (similar to the TDML capability), so if
there is an expected warning that you don't want to cause a failure then you
should suppress that warning. Note that this means that we should check if a
warning is suppressed first, and only if it is not suppressed should it be
escalated to an error.
> option to escalate schema definition warnings to errors
> -------------------------------------------------------
>
> Key: DAFFODIL-2810
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2810
> Project: Daffodil
> Issue Type: New Feature
> Components: Front End
> Affects Versions: 3.4.0
> Reporter: Mike Beckerle
> Assignee: Olabusayo Kilo
> Priority: Major
>
> Just as Java and Scala comiplers have a flag that says to escalate warnings
> to errors, Daffodil needs the same.
> In too many cases, warnings about ignored properties slip through the cracks
> when they really indicate major problems with the schema.
> As an example, DAFFODIL-2809 was about warnings when a dfdlx:repType was
> being ignored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
