[DAFFODIL-2345] Poor diagnostic: out of scope delimiter message - doesn't give element name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 3.7.0
• Component/s: Back End, Diagnostics
• Labels: beginner
• Assignee: Mike Beckerle
• Reporter: Mike Beckerle
• Created: 22/May/20 14:48
• Updated: 29/Mar/24 13:08
• Resolved: 28/Mar/24 18:45

Description

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.