-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop-parsing-error-msg' into develop. Close #96.
**Description** Ogma relies on an existing library for error message reporting of JSON files. That library, by default, provides very plain error messages and the line and column number of the error cannot be customized or contextualized. This causes error messages to seem to apply to a line and column in the file, when they really apply to the line and column of a specific requirement (which may be hard to indentify). **Type** - Feature: improve error reporting messages in parsing of FRET CS JSON files. **Additional context** None. **Requester** - Ivan Perez **Method to check presence of bug** Not applicable (new feature). **Expected result** An error in a requirement in a FRET CS file indicates which requirement it applies to. **Solution implemented** Modify parser to produce name of requirement on parsing errors. Adjust test vectors and examples to include vacuous values in fields that previously had none, since the new implementation is no longer as lazy. **Further notes** None.
- Loading branch information
Showing
7 changed files
with
49 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters