Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Rename command “Go to First Error/Warning” in “Navigate” menu? #9528

Closed
valtlai opened this issue Oct 11, 2014 · 6 comments
Closed

Comments

@valtlai
Copy link
Contributor

valtlai commented Oct 11, 2014

Could it be good if “Go to First Error/Warning” command in “Navigate” menu renamed to “Go to First Issue Problem”?

@valtlai valtlai changed the title Rename command Navigate → “Go to First Error/Warning”? Rename command “Navigate” → “Go to First Error/Warning”? Oct 11, 2014
@valtlai valtlai changed the title Rename command “Navigate” → “Go to First Error/Warning”? Rename command “Go to First Error/Warning” in “Navigate” menu? Oct 11, 2014
@le717
Copy link
Contributor

le717 commented Oct 11, 2014

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.

@valtlai
Copy link
Contributor Author

valtlai commented Oct 12, 2014

@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.

@dangoor
Copy link
Contributor

dangoor commented Oct 27, 2014

Reviewed... it's true that "Problem" is more consistent because that's what the JS Lint errors are called in the panel.

@KarlHeitmann
Copy link

@Jacse, dis you already fix this issue? I'm looking for a starter to bug to start thinkering the source code

@Jacse
Copy link
Contributor

Jacse commented Nov 8, 2014

@KarlHeitmann Yes, I have already fixed this.

@le717
Copy link
Contributor

le717 commented Nov 9, 2014

@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. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants