"It’s only syntax/static checking is done via JSLint with a pretty arcane set of rules. Want to write one line if statements? That’s a warning. A for loop without checking for property existence? That’s a warning."
The JSLint step is optional. I build my Titanium projects via the commandline (I don't use the IDE thing at all) which bypasses JSLint. I use the more reasonable JSHint as integrated into vim, not as part of the build.
There's a difference between reading it and accepting it. More and more people are moving away from JSLint because of the Cry Wolf syndrome - real errors hidden in a sea of warnings based only on the "opinion" that they tend to be harmful coding style.
Comments
"It’s only syntax/static checking is done via JSLint with a pretty arcane set of rules. Want to write one line if statements? That’s a warning. A for loop without checking for property existence? That’s a warning."
Someone hasn't read Javascript: The Good Parts.
The JSLint step is optional. I build my Titanium projects via the commandline (I don't use the IDE thing at all) which bypasses JSLint. I use the more reasonable JSHint as integrated into vim, not as part of the build.
This is the line that builds and runs my project:
You just need to setup the project inside the Titanium Developer app, and then you can invoke it with this command from then on.There's a difference between reading it and accepting it. More and more people are moving away from JSLint because of the Cry Wolf syndrome - real errors hidden in a sea of warnings based only on the "opinion" that they tend to be harmful coding style.
https://github.com/jshint/jshint/