[ 
http://mifosforge.jira.com/browse/MIFOS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

keithwoodlock updated MIFOS-1839:
---------------------------------

    Fix Version/s:     (was: Mifos Backlog)
                   Unscheduled

> Javascript files should be cleaned up
> -------------------------------------
>
>                 Key: MIFOS-1839
>                 URL: http://mifosforge.jira.com/browse/MIFOS-1839
>             Project: mifos
>          Issue Type: Bug
>          Components: Misc
>    Affects Versions: Release 1.1
>         Environment: Platform: All, OS: All
>            Reporter: Keith Pierce
>            Assignee: mifosdeveloperqueue
>             Fix For: Unscheduled
>
>
> On the JSMin web page (http://www.crockford.com/javascript/jsmin.html),
> Douglas Crawford states that JSMin can generate incorrect results for some
> Javascript constructs, but also states that such constructs can be caught by
> running JSLint (http://www.jslint.com/).
>  
> If we haven't done so, we should run JSLint on all Javascript in MifOS, to
> ensure that JSMin does not alter Javascript behavior.
> I ran JSLint on a few Javascript files and found many errors. A large percent 
> of
> errors were "implied global", but some were more serious, and a few made me
> wonder how the file can possibly work (perhaps they are obsolete and not 
> used).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to