Skip to content
This repository has been archived by the owner on May 12, 2020. It is now read-only.

Compiler error messages should not be cropped #77

Open
opyh opened this issue Mar 22, 2015 · 8 comments
Open

Compiler error messages should not be cropped #77

opyh opened this issue Mar 22, 2015 · 8 comments
Assignees

Comments

@opyh
Copy link

opyh commented Mar 22, 2015

Compiler error messages are cropped in the UI:

screenshot 2015-03-22 03 51 44

Have I overlooked a way to see the full error messages somewhere? That would be helpful when debugging, as the important bits are often at the (cut-off) ends of the messages.

Maybe they could just be logged to the console?

Even better would be having inline error messages, like in the linter plugin ;)

@rsteckler
Copy link

Have you found a way to work around this? I'm having a hard time determinging what the compiler is complaining about.

@suda
Copy link
Contributor

suda commented Apr 22, 2015

This will be probably done by implementing #79 or some logging panel. Currently the main goal is updating to latest Atom and fully support upcoming Photon.

@suda suda added the bug label Jun 10, 2015
@cdeadlock
Copy link

I had to do this pain in the arse to see full errors for another problem #110

In atom go to the menu -> View -> Developer -> toggle developer tools
Its just like chrome or chromium developer tools: you can click on the magnifying glass and click on a UI element, and see the source for the full information

@newzealandpaul
Copy link

This is a real pain. Is this being worked on?

@suda
Copy link
Contributor

suda commented Oct 9, 2015

Yes, we're going to introduce error console similar to one in Build IDE.

@rPonuganti
Copy link

This is rea big pain.. I get the error "build didn't produce binary Error: Command faild:.." I could see the full error .. this is minimum is ide that it shows what the error is ..

@dhhagan
Copy link

dhhagan commented Nov 29, 2016

Has this been implemented yet? This is the least lovable Particle Dev feature right now..

@suda
Copy link
Contributor

suda commented Nov 29, 2016

Unfortunately not yet. But it is on top of your Dev priorities!

@suda suda removed this from the 0.1.1 milestone Feb 14, 2017
@suda suda added the confirmed label Feb 14, 2017
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

7 participants