Parse error in LEO file: better reporting, why did it happen?

[metaperl]

I attempted to deploy Leo to a github-pages site and got a blank screen. Using the inspector, I found the following parse error:

leo.js:342 Uncaught (in promise) SyntaxError: Unexpected token 	 in JSON at position 332
    at JSON.parse (<anonymous>)
    at leo.js:342

The file that created the parse error is here:
https://github.com/metaperl/being-doing-having/blob/master/docs/parse-error.leo

it would be nice if parse errors were more prominently fed back to the end user.

[kaleguy]

This is interesting, turns out LeoVue can't handle tabs in the node titles. You have a tab in the title "Isolation-Tank-Gnosis". Remove that and LeoVue can load your file.

I'll upload a fix for this soon. Also good point about error reporting, adding better error message for JSON parse errors.

Also, you have markdown in some of your nodes. To get LeoVue to format the markdown, add @language md to the first line of the node. Child nodes inherit directives, so this can be used to mark a subtree.

[kaleguy]

Pushed a fix for this (tabs in node titles are stripped out) with some better error reporting on console. Will add an error message to UI in future.