[TIMOB-2479] Tooling: Allow Configuration of JSLint
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Trivial |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2013-08-01T00:29:43.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Android |
| Labels | android, feature, ios, rplist, tooling |
| Reporter | Don Thorp |
| Assignee | Ingo Muschenetz |
| Created | 2011-04-15T03:20:51.000+0000 |
| Updated | 2017-03-16T21:28:58.000+0000 |
Description
Please create implementation tickets once this feature has been designed.
JSLint is helpful in warning of potential JS issues. It should
be configurable in tiapp.xml and at least support the
following features.
Configure action per mode. For example in test mode you might want to continue after warnings or errors, in development mode you might want to continue if warnings but not on errors, in production you may want to fail on warnings and errors.
See http://developer.appcelerator.com/helpdesk/view/56271">Helpdesk 56271
+1
also related: http://developer.appcelerator.com/helpdesk/view/65601">Helpdesk 65601
thanks! :-)
The option to disable it completely via tiapp.xml would make several customers happy.
Associated Helpdesk Ticket
http://developer.appcelerator.com/helpdesk/view/63831">http://developer.appcelerator.com/helpdesk/view/63831
Titanium 3.1.1 currently does not use JSLint, nor will it ever. Titanium 3.2.0 uses UglifyJS and that will catch some syntax errors, though UglifyJS doesn't care about coding style. It's possible for someone to write a CLI plugin that runs JSLint, but that's outside the scope of Titanium.
Closing ticket as the issue won't fix.