After creating a JSLint filter to ignore warnings (e.g. `.'Ti(tanium)?' is not defined.`) they are properly filtered; however, they are not ignored. JSLint stops processing files after a certain number of warnings have been reached, and because the warnings are filtered but not ignored they still count against that number. This creates the issue of seeing no warnings but still having JSLint stop processing the file because the limit has been reached.
Customer requests that either the warnings are completely ignored and do not count against the JSLint limit, or that the limit can be modified in the Studio preferences.
In order to test:
- It appears JSLint has a 50 warning limit.
- The problems view should show all 50 errors, and not a smaller number. A shorter number would indicate that it has issues displaying the full list.