This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 131168 [details] Annoying error motivation killing icon I use Netbeans 7.3 Beta 2 and there is no such a problem. The problem appead in 7.3 RC2 In all *.html files in our project 7.3 RC found javascript errors and now marked all the files with error icon, and moreover, this icon is recursivly upstreamed up and up and mark the whole project as errored! We found no way to disable this error icons or disable error checks at all. I repeat - there is no such a problem in 7.3 Beta 2
I think that it's JS issue. But you should provide us that HTML files, which cause that errors for further evaluation. Then simply reopen. Thanks.
it is useless to provide you with these files, cause they 100% contain error for a simple reason - they are templated e.g. var list = [ ##IMAGE_LIST## ]; and this ##IMAGE_LIST## is filled by php script I wonder why beta works with no marks and release works with marks??
I expect that the html code contains something like: <script type="text/javascript"> var list = [ ##IMAGE_LIST## ]; </script> If it's true, then the problem is that the javascript parser reports error here, because it doesn't understand it. Petr is working on the solution, which switch off the reporting in the embedding cases.
The problem is that it is a real error. You have plain HTML file and there is JS containing invalid syntax. In other words it is not a HTML file. Otherwise the error checking would have to be completely disabled.
> which switch off the reporting in the embedding cases that is not help to solve the problem, cause we have html triks as well e.g. <table><tr>##TOP_MENU_CELLS##</tr></table> > In other words it is not a HTML file. we do need html, javascript and other parsers and color syntax as usual in these files moreover, it is OK that it shows errors that is ok!! the problem is that it marks the file with error icon and this icon recursivly repeats up till the project self and therefore all our projects now are marked as errored > Otherwise the error checking would have to be completely disabled. No, no, no, no!! We need to disable small error red subicons in project tree and let everything stay the same. * * * * * * * * * * * * * * * * * * * * * * * * * * I remind you once more, in 7.3 Beta 2 everything is great. The problem in 7.3 RC2 only.
See the image I enclosed to this bug and you get the problem not in error checking, but in project tree.
(In reply to comment #5) > * * * * * * * * * * * * * * * * * * * * * * * * * * > > I remind you once more, in 7.3 Beta 2 everything is great. The problem in 7.3 > RC2 only. Well the way it is in Beta 2 is a bug. Usually users do want to see if they have broken files in their project. Consider somebody really has syntax error in JS file he wants to know the project is broken. So the problem imo is you want to disable it for your particular case where you _know_ and/or _suppose_ your files are ok. There is no such option now.
> Well the way it is in Beta 2 is a bug. No. We used 7.0.1 for a long time and there was no such an icon. > So the problem imo is you want to disable > it for your particular case where you > _know_ and/or _suppose_ your files are ok No, no, no no. We do not want to disable cheking, we want to disable error icons; > There is no such option now. Option is to use 7.3 Beta 2
(In reply to comment #8) > > Well the way it is in Beta 2 is a bug. > > No. > We used 7.0.1 for a long time and there was no such an icon. And that was bug as well. > > > So the problem imo is you want to disable > > it for your particular case where you > > _know_ and/or _suppose_ your files are ok > > No, no, no no. > We do not want to disable cheking, we want to disable error icons; Yep that's what I'm saying: So the problem imo is you want to disable it (error icons) for your particular case where you _know_ and/or _suppose_ your files are ok. Others will report this a defect, because project won't be marked red when there are broken files. > > > There is no such option now. > > Option is to use 7.3 Beta 2 By option I meant configuration option.
for those who wants mannually disable checking there is a file in user dir (see the exact path in About dialog) %netbeans_user_dir%/var/attributes.xml <attributes version="1.0"> <fileobject name="D:|projects|lazychicken|blanks|country.htm"> <attr name="disable_error_checking" boolvalue="true"/> </fileobject> ... </attributes> So, remember, html error check disabling is not stored in the project, it is stored in the user dir folder for netbeans itself.
I think of better way of solving this is to provide some option of ignoring certain files/folders from JS error checking. There are lots of third party libraries that have those JS "errors" and there's nothing a user can do about this. Currently I have this issue with a Symfony 2 project (which BTW, the support for Symfony in NB rocks!) and there are lots of bundles in the vendors folder that have "errors". I am aware there's an option of ignoring a folder completely but this has some unpleasant side effects, like auto-complete not working, and others.
Whether a templating/view language embedded within javascript in an HTML/JSP/foo file is syntactically valid is irrelevant here. The point is that the developer can know better than Netbeans what is and isn't valid (at least I do), and marking a file and/or the entire project as being in error is, at a minimum, counterproductive. This behavior makes working with 7.3 incredibly frustrating, as I can't tell the "real" errors from these ersatz errors.
bftanase and bgunnink, thank you so much for moral support and understanding. I do share completly your feelings about this error icons and hope this "great feature" will be eliminated or at least parametalized in future releases. For now our team is using NB 7.3 Beta 2 and there are no these pleasant error icons!
Created attachment 133269 [details] Mix of HTML + PHP + Javascript
Created attachment 133270 [details] A valid JSON file
Created attachment 133271 [details] Markdown file
Of course the best approach is to provide the option to disable this feature or at least an ignore option. It may be just icons but it can really affect productivity due to confusion and doubts.
Please give us the right to choose if it's a javascript error or not, it kills productivity to see all the project with the error icon just because Netbeans "thinks" that a .js file contains errors.
I am currently suffering countless lost hours of production due to this bug as well... Seriously... We need an option to disable error checking on certain files as the false positives are deeply frustrating... I have filed 2 bugs that are somewhat related... (232196 and 232197) Just need an option to disable those red exclamation marks for certain files.
*** This bug has been marked as a duplicate of bug 233066 ***