unicorn/no-thenable Correctness
What it does
Disallow defining a then property.
Why is this bad?
If an object is defined as "thenable", once it's accidentally used in an await expression, it may cause problems.
Examples
Examples of incorrect code for this rule:
javascript
async function example() {
const foo = {
unicorn: 1,
then() {},
};
const { unicorn } = await foo;
console.log("after"); // <- This will never execute
}Examples of correct code for this rule:
javascript
async function example() {
const foo = {
unicorn: 1,
bar() {},
};
const { unicorn } = await foo;
console.log("after");
}How to use
To enable this rule using the config file or in the CLI, you can use:
json
{
"rules": {
"unicorn/no-thenable": "error"
}
}ts
import { defineConfig } from "oxlint";
export default defineConfig({
rules: {
"unicorn/no-thenable": "error",
},
});bash
oxlint --deny unicorn/no-thenableVersion
This rule was added in v0.0.13.