Closed Gama11 closed 1 year ago
Perhaps the right approach is to test the Lime executable once on boot-up, and to display a message if this occurs. Otherwise, we only log to the console. This could occur due to any code compilation issue in the user's code as well
This could occur due to any code compilation issue in the user's code as well
Such as? I can't think of any other scenario where lime display
would fail / exit with 1.
I think it's actually good that this pops up in an error box so it doesn't fail silently anymore, it's just that the hints don't help much here (neither lime setup nor lime.executable will do much good). Perhaps we should check if the output begins with Error:
and show the error in the popup box instead in that case.
Another example:
The startsWith("Error:")
check might be a good heuristic.
The new 1.5.0 update of lime-vscode-extension includes a better experience when lime display
fails.
This is a case where the new error is perhaps a bit misleading:
Too bad Lime handles
-lib
on its own, otherwise it could just be passed onto the Haxe Language Server, which would then create a proper diagnostic from it in the problems view. But I guess there isn't really a way forlime display
not to fail here because of its custom lib handling...