1. #1
    Sencha User hobophobik's Avatar
    Join Date
    Jul 2010
    Location
    UK
    Posts
    22
    Vote Rating
    0
    hobophobik is on a distinguished road

      0  

    Default JSLint

    JSLint


    Hi,

    I've just completed installing SpiderMonkey on Centos so that I can run JSLint from the command line. So far it has proved a fantastic way to spot those annoying little extra commas that break our javascript in IE.

    For a bit of amusement I decided to fire the Ext 3.2.1 source code through the tests; 99 files were perfect, while 182 files failed with at least one error.

    Does anyone have any opinons about how strictly we should adhere to the amendments suggested in the JSLint output?

    Cheers,
    Hobo

  2. #2
    Sencha - Community Support Team VinylFox's Avatar
    Join Date
    Mar 2007
    Location
    Baltimore, MD
    Posts
    1,501
    Vote Rating
    7
    VinylFox will become famous soon enough VinylFox will become famous soon enough

      0  

    Default


    Typically I use "The Good Parts" settings, but with "evil: true" included.

  3. #3
    Sencha - Community Support Team mschwartz's Avatar
    Join Date
    Nov 2008
    Location
    San Diego, Peoples' Republic of California
    Posts
    2,053
    Vote Rating
    17
    mschwartz will become famous soon enough mschwartz will become famous soon enough

      0  

    Default


    JSLint is a great help, but it's not perfect. In some functions, it will complain that not all paths return a value, but you do want it to return undefined for the path it complains about.

    http://community.activestate.com/xpi...-jslint-komodo

    ^^^ awesomeness.

  4. #4
    Sencha User hobophobik's Avatar
    Join Date
    Jul 2010
    Location
    UK
    Posts
    22
    Vote Rating
    0
    hobophobik is on a distinguished road

      0  

    Default


    Hmm yes, I just tried it on our code with "The good parts".

    white: true, onevar: true, undef: true, nomen: true, eqeqeq: true, plusplus: true, bitwise: true, regexp: true, newcap: true, immed: true
    That's a lot of "Missing space after :" I'd have to fix. Also, due to the way I've split up classes into individual files, I get a lot of 'X is not defined' :/

  5. #5
    Sencha User hobophobik's Avatar
    Join Date
    Jul 2010
    Location
    UK
    Posts
    22
    Vote Rating
    0
    hobophobik is on a distinguished road

      0  

    Default


    Shame, I stopped using Komodo a few months ago... vim all the way now

  6. #6
    Sencha - Community Support Team mschwartz's Avatar
    Join Date
    Nov 2008
    Location
    San Diego, Peoples' Republic of California
    Posts
    2,053
    Vote Rating
    17
    mschwartz will become famous soon enough mschwartz will become famous soon enough

      0  

    Default


    http://www.vim.org/scripts/script.php?script_id=2729

    seems up to date.

    For JavaScript, I love how Komodo highlights syntax errors as I type/edit.

    vim is VERY powerful though.

Similar Threads

  1. JSLint for Version 1.0 ?
    By torsten.t in forum Sencha Touch 1.x: Discussion
    Replies: 1
    Last Post: 8 Nov 2010, 10:40 AM
  2. JSLint new Array() ? (Solved)
    By michaelc in forum Ext 3.x: Help & Discussion
    Replies: 7
    Last Post: 10 Sep 2010, 11:28 PM
  3. Comma convention JSlint
    By emredagli in forum Community Discussion
    Replies: 7
    Last Post: 14 Oct 2009, 5:52 AM
  4. [2.x svn4408] JSLint errors
    By Condor in forum Ext 2.x: Bugs
    Replies: 0
    Last Post: 16 Jun 2009, 1:22 AM

Thread Participants: 2

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar