These error messages were a bit short and contained technical jargon. They did not give the user a good sense of how to proceed.
With this commit, the error messages are changed to clearly include the important elements of a good error message:
- What went wrong
- Why it happened
- How they can fix it themselves
- How they can report the issue to get it permanently fixed for everyone
To do this, the setError() function is extended to also be able to accept optional explanation and bugReportUrl arguments, which are used to present better information to the user.
|"Tool not found" error message|
|"Tool crashed" error message|