Originally reported byLuca Geretti (Bitbucket: lgeretti, GitHub: lgeretti)
In order to enable the checking of a file-type definition of an automaton, list the issues that may be possible when defining a single automaton. Organize them as warnings (non-blocking) and errors (blocking), also providing the scope of blocking in the second case (allows to check for multiple errors on different sections of the definition file, without generating at the same time a large amount of errors.
Originally reported by Luca Geretti (Bitbucket: lgeretti, GitHub: lgeretti)
In order to enable the checking of a file-type definition of an automaton, list the issues that may be possible when defining a single automaton. Organize them as warnings (non-blocking) and errors (blocking), also providing the scope of blocking in the second case (allows to check for multiple errors on different sections of the definition file, without generating at the same time a large amount of errors.