eslint over assets/js/ returns 0 errors but 73 warnings, with two notable clusters:
~20 no-empty: silently swallowed catch {} blocks. Worth a pass to at least console.debug/comment why each is intentionally ignored — a couple appear to mask real fetch failures rather than known-benign cases (e.g. Date parsing).
~6 eqeqeq: loose ==/!= instead of ===/!== in dashboard.js/ticket.js (e.g. data.comment_id == x), comparing values of possibly-differing types. Low risk today but an easy source of a future type-coercion bug.
phpcs --standard=.phpcs.xml across the whole tree is clean (0 violations) — this issue is JS-only.
Fix: Sweep the empty catches to add at minimum a comment explaining why the error is safely ignored (or log it), and switch the flagged loose comparisons to strict equality.
**Severity:** Low
`eslint` over `assets/js/` returns 0 errors but 73 warnings, with two notable clusters:
- **~20 `no-empty`**: silently swallowed `catch {}` blocks. Worth a pass to at least `console.debug`/comment why each is intentionally ignored — a couple appear to mask real fetch failures rather than known-benign cases (e.g. `Date` parsing).
- **~6 `eqeqeq`**: loose `==`/`!=` instead of `===`/`!==` in `dashboard.js`/`ticket.js` (e.g. `data.comment_id == x`), comparing values of possibly-differing types. Low risk today but an easy source of a future type-coercion bug.
`phpcs --standard=.phpcs.xml` across the whole tree is clean (0 violations) — this issue is JS-only.
**Fix:** Sweep the empty catches to add at minimum a comment explaining why the error is safely ignored (or log it), and switch the flagged loose comparisons to strict equality.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: Low
eslintoverassets/js/returns 0 errors but 73 warnings, with two notable clusters:no-empty: silently swallowedcatch {}blocks. Worth a pass to at leastconsole.debug/comment why each is intentionally ignored — a couple appear to mask real fetch failures rather than known-benign cases (e.g.Dateparsing).eqeqeq: loose==/!=instead of===/!==indashboard.js/ticket.js(e.g.data.comment_id == x), comparing values of possibly-differing types. Low risk today but an easy source of a future type-coercion bug.phpcs --standard=.phpcs.xmlacross the whole tree is clean (0 violations) — this issue is JS-only.Fix: Sweep the empty catches to add at minimum a comment explaining why the error is safely ignored (or log it), and switch the flagged loose comparisons to strict equality.