| Issue 186: | Make jquery.jmesa.js "lint free" | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I think that it is not a bad idea to modify JMesa's javascript to make it
be able to pass JSLint's validator using "The Good Parts" button.
Mostly this involves several changes:
1) Scoping the inadvertently global variable 'classes' so that it local instead
2) Changing '==' and '!=' to '===' and '!=='
3) Using [] and {} instead of 'new Array()' and 'new Object()'
along with a few other small tweaks and whitespace rules. Obviously, the
javascript is working fine as it is, but JSLint is good at catching common
JavaScript error that occur because of its dynamic nature (like #1 above)
and its forgiving parser.
I don't want to hold up the next release for this, but I have already made
the changes and I am testing them in my own project right now. The only
thing that I will need help testing the worksheet because I don't use that yet.
What do you think?
Apr 2, 2009
Project Member
#1
jeff.johnston.mn@gmail.com
Status:
Accepted
Apr 2, 2009
actually, I'm not so confident yet, I just wanted to see what you thought of the idea. To run JSLint I usually just go to jslint.com, paste in the code, hit "The Good Parts" button and then hit the "JSLint" button. I'm sure there's a way to integrate it into ant using Rhino (which I think we have in the repository already, right?)
Apr 2, 2009
How about if we wait until after the next release then...I'll do a release this weekend. We get JMesa lint free after that! Yep, Rhino is under the name js-1.7R1.jar.
Apr 13, 2010
(No comment was entered for this change.)
Status:
WontFix
|