| Error in editor not propagating in PHP explorer tree [message #98064] |
Thu, 04 June 2009 14:53  |
Eclipse User |
|
|
|
Originally posted by: nomail.nomail.it
I did a configuration I must reproduce, but I don't remember what I did! :-p
I change something, so that the errors in js and html files are shown only
into the editor screen and not on the tree. In the tree I only see errors of
php files.
Some ideas?
|
|
|
| Re: Error in editor not propagating in PHP explorer tree [message #98107 is a reply to message #98064] |
Fri, 05 June 2009 05:42  |
| Eclipse User |
|
|
|
Originally posted by: nomail.nomail.it
Found! And that was also the cause of the problem I previously asked:
Project properties->javascript->javascript libraries->source
exclude all (or include a non existing type).
As a side effect, like validation on the tree, also //TODO stop working.
So the question is converted into: how to stop the js validator mantaining
//TODO working?
Javascript validator is USELESS. Too many inexistent errors: doesn't
understand jQuery; doesn't understand js inclusions giving "cannot resolved
to a type"; doesn't understand some kind o multi-line declaration like those
into jQuery core, and many other things that generates tons of red errors
and warnings.
jQuery itself has more than 100 errors, TinyMce editor has tons...
everything has errors.
Using shorcuts > and < on breakpoints is impossibile because it stop on
every error/warning.
So I prefer stopping any js validation.Do you know how, leaving //TODO
working, and/or eventually having the possibiliti to scan 1 file at a time
manually?
"Rik" <nomail@nomail.it> ha scritto nel messaggio
news:h0954e$ad1$1@build.eclipse.org...
>I did a configuration I must reproduce, but I don't remember what I did!
>:-p
>
> I change something, so that the errors in js and html files are shown only
> into the editor screen and not on the tree. In the tree I only see errors
> of php files.
>
> Some ideas?
>
|
|
|
Powered by
FUDForum. Page generated in 0.03757 seconds
Home