This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
chore(*): enable jshint eqeqeq #14287
Comments
@lgalfaso So, in parse there's actually a comparison that seems to be == / != on purpose: Lines 1532 to 1543 in aa077e8
angular.js/test/ng/parseSpec.js Line 1741 in aa077e8
|
Seems like we are missing a test, e.g. |
That's right, thanks @gkalpak |
Narretz
added a commit
to Narretz/angular.js
that referenced
this issue
Mar 24, 2016
Add jshint "eqeqeq" and "eqnull" rules (to allow == null comparisons). Only adds it to files under src/, because we these files are unit-tested. Files in src/ngLocale are excluded, because the code is imported. Closes angular#14287
Narretz
added a commit
to Narretz/angular.js
that referenced
this issue
Mar 25, 2016
Add jshint "eqeqeq" and "eqnull" rules (to allow == null comparisons). Only adds it to files under src/, because we these files are unit-tested. Files in src/ngLocale are excluded, because the code is imported. Closes angular#14287
Narretz
added a commit
to Narretz/angular.js
that referenced
this issue
Mar 25, 2016
Add jshint "eqeqeq" and "eqnull" rules (to allow == null comparisons). Only adds it to files under src/, because we these files are unit-tested. Files in src/ngLocale are excluded, because the code is imported. Closes angular#14287
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add jshint eqeqeq and eqnull rules, and fix all resulting errors.
The text was updated successfully, but these errors were encountered: