Syntax errors are currently very difficult to resolve. Syntax errors will be the most common experience when people use the pluto and thus these will need to be addressed at some point.
I currently see two solutions to the current situation:
translating the errors to a concise meaningful message
providing location info (position in file) of where the error originated
Position info while more difficult to implement can provide more information to a user even if that position information is attached to a cryptic error message.
Position info can be gathered if the edn is read with tools.analyzer on the client.
Syntax errors are currently very difficult to resolve. Syntax errors will be the most common experience when people use the pluto and thus these will need to be addressed at some point.
I currently see two solutions to the current situation:
Position info while more difficult to implement can provide more information to a user even if that position information is attached to a cryptic error message.
Position info can be gathered if the edn is read with tools.analyzer on the client.