# Click on errors

**URL:** <https://discourse.codecombat.com/t/click-on-errors/3892>\
**Category:** Uncategorized\
**Created:** [May 13, 2015, 6:30pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892 "2015-05-13T18:30:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![atnatenshon](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@atnatenshon](https://discourse.codecombat.com/u/atnatenshon)\
**Post date:** [May 13, 2015, 6:30pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892/1 "2015-05-13T18:30:32Z")

</div>

Not sure where to put feature requests, but when you have a error in your code it would be very nice to click on the error to see a definition or how to solve.

Thanks

AT

---

<div class="post-metadata">

**Author:** ![Magicfloatincow](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.codecombat.com/magicfloatincow/32/3855_2.png) [@Magicfloatincow](https://discourse.codecombat.com/u/Magicfloatincow)\
**Post date:** [May 13, 2015, 6:37pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892/2 "2015-05-13T18:37:13Z")

</div>

That actually would be good idea if someone can add that onto the website that actually would help everyone out.

---

<div class="post-metadata">

**Author:** ![ChronistGilver](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.codecombat.com/chronistgilver/32/3778_2.png) [@ChronistGilver](https://discourse.codecombat.com/u/ChronistGilver)\
**Post date:** [May 13, 2015, 7:05pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892/3 "2015-05-13T19:05:40Z")

</div>

Giving how to solve a problem would defeat the purpose of coding, wouldn’t you think? And besides, the name of the error, followed by the red-highlighted line, is usually enough to solve the problem.

---

<div class="post-metadata">

**Author:** ![Magicfloatincow](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.codecombat.com/magicfloatincow/32/3855_2.png) [@Magicfloatincow](https://discourse.codecombat.com/u/Magicfloatincow)\
**Post date:** [May 13, 2015, 7:17pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892/4 "2015-05-13T19:17:21Z")

</div>

Or or or or… after like 500 retries you get 5 hints ;-;

---

<div class="post-metadata">

**Author:** ![atnatenshon](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@atnatenshon](https://discourse.codecombat.com/u/atnatenshon)\
**Post date:** [May 13, 2015, 7:21pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892/5 "2015-05-13T19:21:29Z")

</div>

I think I have to disagree, people get coaching and feedback specifically to help them improve and having incomplete or non-informative feedback seems counter productive, at the very least an error definition or explanation would help improve understanding.

---

<div class="post-metadata">

**Author:** ![ChronistGilver](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.codecombat.com/chronistgilver/32/3778_2.png) [@ChronistGilver](https://discourse.codecombat.com/u/ChronistGilver)\
**Post date:** [May 13, 2015, 7:24pm UTC](https://discourse.codecombat.com/t/click-on-errors/3892/6 "2015-05-13T19:24:05Z")

</div>

Very well. I see your point, I was merely pointing out that giving away the solution would be counter-productive, in my opinion.

---

<div class="post-metadata">

**Author:** ![atnatenshon](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@atnatenshon](https://discourse.codecombat.com/u/atnatenshon)\
**Post date:** [May 14, 2015, 12:59am UTC](https://discourse.codecombat.com/t/click-on-errors/3892/7 "2015-05-14T00:59:30Z")

</div>

Agreed, it is less about an answer and more about an explanation for the error.

---

<div class="post-metadata">

**Author:** ![Vlevo](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.codecombat.com/vlevo/32/2074_2.png) [@Vlevo](https://discourse.codecombat.com/u/Vlevo)\
**Post date:** [May 14, 2015, 2:46am UTC](https://discourse.codecombat.com/t/click-on-errors/3892/8 "2015-05-14T02:46:31Z")

</div>

some of the error messages are very vague . . . but that is actually true of every compiler I have ever had the pleasure to work with.