Detected the
delete operator with computed key expressions JS-0320
Anti-pattern
Minor
6 months ago
—
6 months old
Do not delete dynamically computed property keys
11 store[key] = value
12 },
13 removeItem: (key: string): void => {
14 delete store[key]15 },
16 clear: (): void => {
17 store = {}
Description
Deleting dynamically computed keys can be dangerous and in some cases not well optimized.
Using the delete operator on keys that aren't runtime constants could be a sign that you're using the wrong data structures.
Using Objects with added and removed keys can cause occasional edge case bugs, such as if a key is named "hasOwnProperty".
Consider using a Map or Set if you’re storing collections of objects.
Bad Practice
// Can be replaced with the constant equivalents, such as container.aaa
delete container['aaa'];
delete container['Infinity'];
// Dynamic, difficult-to-reason-about lookups
const name = 'name';
delete container[name];
delete container[name.toUpperCase()];
Recommended
const container: { [i: string]: number } = {
/* ... */
};
// Constant runtime lookups by string index
delete container.aaa;
// Constants that must be accessed by []
delete container[7];
delete container['-Infinity'];