| Summary: | Confusing tern error messages | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | JS Tools | Assignee: | Michael Rennie <Michael_Rennie> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Carolyn_MacLeod, libingw |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
John Arthorne
I kind of disagree with making error messages more generic, because that often comes back to bite us later when users don't have enough information. Perhaps the error messages can be improved so that they are clearer, for example, if "server not started" does in fact mean the Tern server, then the error message needs to make that clear. Pretty much all of the 'failed*' messages are not shown to the user in the IDE, they get logged to the console (with just enough info so that if someone filed a bug I could immediately know where the tools failed). I NLS'd them so we were not dumping english-only traces to the console. If the Orion scheme is to always log to the console in English, I can easily un-NLS them. Libing, do we NLS messages that are dumped to the console if we can? Or do we try to keep console messages in English? Closing worksforme, as I noted, the only place that you could ever potentially see one of the messages is in the console. |