Ticket #10901 (closed PLIP: fixed)
|Reported by:||smcmahon||Owned by:||smcmahon|
Description (last modified by smcmahon) (diff)
Proposer: Steve McMahon
Seconder: none yet
JSLint can be used to check compliance with these coding standards.
Cleaning up existing code isn't terribly difficult.
Proposal & Implementation
Clean up the existing scripts, starting with those in the ecmascripts skin folder in Plone itself, then moving on to the plone.app.* and plone.* spaces. I wouldn't bother with archetypes or third-party components like KSS.
It should also be possible to implement a test suite, possibly using something like Hudson, to find regressions.
This PLIP would probably be a nice fit with the PLIP to move third-party js into the collective, since it would be easier to identify what's our own code.
Documentation in developer manual. Cleaned up scripts. Test suite.
Breaking code in the course of cleaning it up. This is no small risk given our lack of browser-level test coverage for most of the js components.
Steve McMahon Others needed!
comment:10 Changed 5 years ago by esteele
- Status changed from assigned to closed
- Resolution set to fixed