-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Rename command “Go to First Error/Warning” in “Navigate” menu? #9528
Comments
Can you explain your reasoning behind that? "Issue" can sometimes mean many things (for a good example, the GitHub Issues system we are using contain multiple kinds of "issue" reports, such as usability, extensibility, etc.), but "error" or "warning" is more specific. Further, that dialog goes to the first place an error has occur or warning was thrown, not a usability error that might be noted in a comment with a link to the bug tracker ticket. I'd support removing the forward slash in the message ("Go to First Error" sounds better to me) though. |
@le717 I was supposed to write “problem”, not “issue”. I think “Go to First Problem” would be better because errors and warnings are called ‘problem’ on the linting panel. |
Reviewed... it's true that "Problem" is more consistent because that's what the JS Lint errors are called in the panel. |
@Jacse, dis you already fix this issue? I'm looking for a starter to bug to start thinkering the source code |
@KarlHeitmann Yes, I have already fixed this. |
@KarlHeitmann If you are looking for a starter bug to tackle, feel free to browse through the starter bug label and pick one you link. 👍 |
Could it be good if “Go to First Error/Warning” command in “Navigate” menu renamed to “Go to First
IssueProblem”?The text was updated successfully, but these errors were encountered: