-
Export/import JSON: Error Handling
The export/import feature is really great and can be a very big step!
But I feel slightly uncomfortable with the overall error handling.
If one of the goals is to be able to export a library to SVN, then – from my point of view – it must be possible to export/import erroneous classes too.
If we talk about SVN we do not talk about perfect code. We even do not talk about valid code.
We talk about a current state of development. This means exporting a class containing “#???” for example
should be a valid export. A missing superclass also should not prevent the export.
There needs to be some kind of error reporting (export_errors.json) and maybe an additional info in the json of the corresponding, erroneous class.
Another scenario might be bigger projects with external developers, when not every developer has access to the complete code. So, missing superclasses for example can be quite normal.
At least, we need options to ignore those “problem childs”
What about a learner’s guide “The 20 most common mistakes in writing omnis code?” It’ll never be possible to export this one 😉
Another interesting side effect is the “error detection”. Many of the errors reported by the export tool are usually ignored by the interpreter. And there is no tool to find them.
Therefore, we need an improved “Method Checker” or – even better – some kind of “Library Checker” to ensure code quality.
Well, hm…wondering what others think about this … -
0 Replies
Sorry, there were no replies found.
Log in to reply.
