Just pushed a build up that eliminates a minor annoyance. If you now click on an error's file and line number, you will get a popup modal that loads up the file in which the error occurred, and highlights the line at which the error occurred.
Only a minor enhancement, but let's you avoid the little dance that you have to do: Alt+Tab / Cmd+Tab to your editor, open the right file, and jump to the right line.
This is only available when the error occurs in an external JS file, since inline-scripts may be on dynamic pages and the line numbers may be off. But it shouldn't affect you because you don't write any of that dirty inline code, right? Right? :)
Only a minor enhancement, but let's you avoid the little dance that you have to do: Alt+Tab / Cmd+Tab to your editor, open the right file, and jump to the right line.
This is only available when the error occurs in an external JS file, since inline-scripts may be on dynamic pages and the line numbers may be off. But it shouldn't affect you because you don't write any of that dirty inline code, right? Right? :)
Hi,
ReplyDeleteI've signed up for a free account and can't figure where-else I could post my question: what is Muted Errors ?
Ah. I must really come up with a way to ask and answer such ad-hoc questions. If you have any suggestions for any services that help with this, do let me know.
ReplyDeleteNow, to answer your question: Muted errors are errors that we've caught, but you probably don't care about, so they are removed from your regular list of errors. These include errors that might not have sufficient information for one reason or another, or errors in common JS snippets people use all the time - things like Google Analytics of Facebook's Like buttons - errors which you can't fix anyway. In other words, Muted errors is just a way to hide away crap errors so that you can focus on the ones that really matter.