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.

Bug 238782 - Allow to ignore file errors in parts of a project [because of top level error badges]
Summary: Allow to ignore file errors in parts of a project [because of top level error...
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: Editing infrastructure (show other bugs)
Version: 7.4
Hardware: PC Linux
: P2 normal with 15 votes (vote)
Assignee: Milutin Kristofic
: 237706 (view as bug list)
Depends on:
Reported: 2013-11-25 15:15 UTC by oyviste
Modified: 2016-12-03 11:12 UTC (History)
4 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description oyviste 2013-11-25 15:15:25 UTC
Need a more flexible way to selectively hide/ignore sources of errors because of the top level error badges.

Our projects incorporate third-party code, mostly JS, CSS and HTML, and to get rid of error badges originating from those parts, I had to change the MIME-type of *.html, *.css and *.js globally in Netbeans to "text/plain". This also removes the association with specialized editors for those types. I think that is an unnecessary sacrifice just to get rid of errors from code I never intend to touch. In short, the error badges are nice, but not flexible enough for large projects, where one might not care about all in-tree errors and would like to just ignore some of them completely.

Also, if Netbeans happens to falsely detect errors for some file type X, when in fact there is no real error, it would be nice to have the option to ignore it right away, instead of waiting for a fix to land in a future Netbeans version.

If a set of paths/subdirs could be excluded as "sources" of top level error badges on a per project basis, that would solve the need in our case. Some kind of filtering, so a developer can optionally control what can cause error badges to be stamped on the entire project.

See also this bug, which is specifically for the PHP-case, but still contains comments from others with a similar desire for a general fix:

I selected "projects / Generic infrastructure" for bug Product/Component, please correct me if I am wrong.
Comment 1 Milos Kleint 2013-11-25 15:39:52 UTC
definitely not project system code itself. Also not sure if specific project type can influence this. That would be the language support that should either interfere on the specific side of individual errors or on the global level of error propagation
Comment 2 oyviste 2013-11-25 18:12:51 UTC
Since product has been set to "web": it was not my intention to request this only for web specific file types, if that matters. I merely used those types as an example. I was thinking more in the line of a general mechanism for filtering or stopping error [badge] propagation at configurable paths in a project.
Comment 3 ryan_jake 2013-11-25 18:23:41 UTC
I'm pasting in an edited version of my comment about this from ... as it applies more directly to this thread (and may help for context).


Anyway, IMHO, the addition of a new configuration option, to *compliment* the new "error badge in menu tree" feature may really reduce a lot of ongoing overhead in the issue queues. Perhaps such an option belongs in "Options > Editor > General" or "Options > Editor > Hints" and could be something like:

Error Badge Display in Project/File Trees:
- Disable
- Enable on files
- Enable on files and parents recursively

Sure, it would be nice if something like this could be configured on a project-by-project and path-by-path basis, or if it could be setup to only apply to various mimetypes, etc., but at the very least having a global option for this would be quite helpful.
Comment 4 Vladimir Riha 2013-11-26 15:25:47 UTC
*** Bug 237706 has been marked as a duplicate of this bug. ***
Comment 5 capistrano.tiago 2013-12-04 11:23:24 UTC
possibility to add a expression to the "dictionary", to not show hints anymore, will be useful for developers that use tags in html.

<input type="text" id="datai" #{MASK:99/99/9999}>

"#{MASK:99/99/9999}" could be added to dictionary to not show hints anymore.

Sorry for my english!
Comment 6 oyviste 2015-03-05 08:06:27 UTC
So another example of the type of situation that this issue is all about: one of our frontend developers decided to start using SASS CSS preprocessor in a  project. I don't work on the CSS bits at all, but now Netbeans 8.0.2 wrongly reports parsing errors in some scss files (they do compile just fine with official SASS). So I now have the entire project stamped with "Contains files with errors", even though it does not concern me at all ! Clearly the Netbeans parser for .scss files has issues [1], and as a result I should be able to exclude .scss files from error badge reporting until this is fixed in Netbeans.

Comment 7 PunchyRascal 2016-12-03 11:12:08 UTC
I think simply disabling error badge when the corresponding error is marked as ignored in the specific file is the best solution here. However, I don't see an option to ignore PHP parsing error, only HTML, CSS.