search

Garthanos / geoxml

Automatically exported from code.google.com/p/geoxml
1 stars 0 forks source link

Make use of JSLint to identify potential javascript errors #19

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If you run geoxmlfull.js from SVN through http://jslint.com/ there are a
huge number of potential problems identified.

I would suggest putting a command line version of JS Lint as part of your
build process, and slowly moving towards 0 errors.

Original issue reported on code.google.com by daniel.o...@gmail.com on 2 Sep 2009 at 10:03

GoogleCodeExporter commented 9 years ago 
and some of the things it identifies as errors are nonsense like line breaking 
errors... 

and others "fixing" some of those "errors" causes the
code to not work if you can tell me why find and replace on
!= null to !== null just doesnt work? I'd like to know

that aside it does look like something I did recently
added some that I dont consider acceptable has manage to
sneak in.

Original comment by lanceala...@gmail.com on 17 Sep 2009 at 9:42