[CLOSED] Rename command “Go to First Error/Warning” in “Navigate” menu?

[core-ai-bot]

Issue by valtlai
Saturday Oct 11, 2014 at 15:04 GMT
Originally opened as adobe/brackets#9528

---

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

[core-ai-bot]

Comment by le717
Saturday Oct 11, 2014 at 17:22 GMT

---

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.

[core-ai-bot]

Comment by valtlai
Sunday Oct 12, 2014 at 15:06 GMT

---

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

[core-ai-bot]

Comment by dangoor
Monday Oct 27, 2014 at 18:50 GMT

---

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

[core-ai-bot]

Comment by KarlHeitmann
Saturday Nov 08, 2014 at 15:51 GMT

---

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

[core-ai-bot]

Comment by Jacse
Saturday Nov 08, 2014 at 16:50 GMT

---

@KarlHeitmann Yes, I have already fixed this.

[core-ai-bot]

Comment by le717
Sunday Nov 09, 2014 at 21:21 GMT

---

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