Ticket #60 (checkedin enhancement)
Reporter  Reid Burke |
Opened: 04/17/12 Last modified: 04/23/12 Status: checkedin Type: enhancement Resolution: fixed |
Owner Reid Burke |
Target Release: 0.2.2 Priority: P3 (normal) |
|---|---|---|---|
| Summary: | Fix code problems reported by the linter | ||
| Description: | Sprint 7 will include contributions from other teams. A part of the checklist* for contributing is having code pass the linter. Yeti's `make lint` should pass without error in preparation for others contributing to Yeti. |
||
| Type: | enhancement | Observed in Version: | development master |
| Component: | Yeti | Severity: | S3 (normal) |
| Assigned To: | Reid Burke | Target Release: | 0.2.2 |
| Location: | Library Code | Priority: | P3 (normal) |
| Tags: | Relates To: | ||
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 04/17/12
|
|
Posted: 04/17/12
|
|
Posted: 04/23/12
Closing out bugs checked in to 0.2.2. |
Checked in yesterday.
Yeti switched to the JSHint linter from JSLint. Yeti runs JSHint with some strict options, including the enforcement of Crockford whitespace:
https://github.com/yui/yeti/commit/913fd3f233c9e85d77056ac4ce0dc9632d412766#diff-0
Yeti has been changed to come into compliance with these options and currently passes lint.
The use of JSLint will be re-evaluated in the future. I will continue to periodically run JSLint side by side with JSHint to better understand the differences between the two systems. This feedback will be part of our team's planned roundtable discussion about JSLint with Doug.