Found empty block statements JS-0009
Anti-pattern
Minor
5 months ago
—
3 years old
Empty block statement
6824 const i = require('underscore')
6825 try {
6826 n = require('jquery')
6827 } catch (r) {} 6828 t(e, exports, i, n)
6829 } else e.Backbone = t(e, {}, e._, e.jQuery || e.Zepto || e.ender || e.$)
6830})(function (t, e, i, n) {Empty block statement
5211 (k.ajaxSettings.xhr = function () {
5212 try {
5213 return new C.XMLHttpRequest()
5214 } catch (e) {} 5215 })
5216 const Ut = { 0: 200, 1223: 204 }
5217 let Xt = k.ajaxSettings.xhr();Empty block statement
3321 (k.cleanData(ve(t, !1)), (t.innerHTML = e))
3322 }
3323 t = 0
3324 } catch (e) {} 3325 }
3326 t && this.empty().append(e)
3327 },Empty block statement
84 if (checksum.toString() == newChecksum.toString()) {
85 isWif = true
86 }
87 } catch (e) {} 88 return isWif
89}
90Empty block statement
2587 (function () {
2588 try {
2589 return E.activeElement
2590 } catch (e) {} 2591 })()) ==
2592 (t === 'focus')
2593 )
Description
Empty block statements, while not technically errors, usually occur due to refactoring that wasn't completed. They can mislead the reader.
If you still want to keep an empty block, add a comment saying empty inside the block.
Bad Practice
if (someCheck) {}
while (someCheck) {}
try {
doSomething();
} catch(err) {
} finally {
}
Recommended
if (someCheck) {
// empty
}
while (someCheck) {
/* empty */
}
try {
doSomething();
} catch (err) {
// continue regardless of error
}
try {
doSomething();
} finally {
/* continue regardless of error */
}