[ https://issues.apache.org/jira/browse/DAFFODIL-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831100#comment-17831100 ]
Mike Beckerle commented on DAFFODIL-2345: ----------------------------------------- See https://github.com/apache/daffodil/pull/1195 > Poor diagnostic: out of scope delimiter message - doesn't give element name > --------------------------------------------------------------------------- > > Key: DAFFODIL-2345 > URL: https://issues.apache.org/jira/browse/DAFFODIL-2345 > Project: Daffodil > Issue Type: Bug > Components: Back End, Diagnostics > Affects Versions: 2.6.0 > Reporter: Mike Beckerle > Assignee: Mike Beckerle > Priority: Major > Labels: beginner > Fix For: 3.7.0 > > > When scanning for a separator and encountering an out-of-scope > separator/terminator, the diagnostic message is really poor. > It says what it found, that it was out-of-scope, but doesn't focus you on > where it was within the scope, by giving an element name, or line number in > the schema. > If you have a required element that is missing, so that the parser can't find > that element's separator and instead finds the enclosing > separator/terminator, the diagnostic message needs to include the required > element that it did not find a separator before, or the prior element it did > not find the separator after. One of the two. Or at least needs to point you > at the sequence the two elements are found in. But since that sequence could > be spread over many lines, it really does need to identify in terms of the > term decl before and after where the separator was not found. -- This message was sent by Atlassian Jira (v8.20.10#820010)