All of our javascript should pass eslint testing - currently it does not. This fails were introduced by #1963340: Change field UI so that adding a field is a separate task. Seems like #2393391: JS Follow-up to #1963340 did not catch everything :)
8.0.x alex: ~/dev/drupal > eslint ./
core/modules/field_ui/field_ui.js
31:28 error Expected '!==' and instead saw '!=' eqeqeq
41:20 error Expected '!==' and instead saw '!=' eqeqeq
✖ 2 problems
| Comment | File | Size | Author |
|---|---|---|---|
| d8-field-ui-js-standards.patch | 938 bytes | alexpott |
Comments
Comment #1
daffie commentedWe use for Drupal ESLint testing for javascript. The rules for the use of === and !== is that it is good practice to use them instead of their regular counterparts == and !=.
It all looks good to me and it is a very simple patch, so RTBC for me.
Comment #2
nod_This is included in #2389515: Update ESLint rules. I'd rather get that other issue reviewed and committed.
Comment #3
webchickWell, it's been over a week and that issue's still outstanding and this one's tiny and ready to go, so...
Committed and pushed to 8.0.x. Thanks!