Error message detail

[martindusinberre]

If there's some kind of error which is preventing the importer from functioning, it would be wonderful if we could have some kind of message showing not only the page (e.g. 2.4.4.2/textComponent.json) but also the line number. This would speed things up a lot and also help identify if there's a problem like the "hidden character" Christian found last week.

[martindusinberre]

A good example has just come up: the log is saying that there's an unexpected right bracket at position 426 on 2.4.2.2. pT2, but I just can't see it. Unless I've read the log wrongly. But you see the problem either way--something I've done has just crashed the system.

[interrogator]

The tool identifies two main types of errors: syntax errors (i.e. invalid JSON) and content errors (i.e. incorrect or missing data types).

For syntax errors, you will get the line and column (i.e. number of characters into the line) where the error was found.

For content errors, this is not totally possible, because the data by this point has been read into an object that has no 'lines'. Even so, it will tell you which key/value is missing/incorrect, and what it should be.