promise/no-callback-in-promise Correctness
What it does
Disallows calling a callback function (cb()) inside a Promise.prototype.then() or Promise.prototype.catch().
Why is this bad?
Directly invoking a callback inside a then() or catch() method can lead to unexpected behavior, such as the callback being called multiple times. Additionally, mixing the callback and promise paradigms in this way can make the code confusing and harder to maintain.
Examples
Examples of incorrect code for this rule:
function callback(err, data) {
console.log("Callback got called with:", err, data);
throw new Error("My error");
}
Promise.resolve()
.then(() => callback(null, "data"))
.catch((err) => callback(err.message, null));Examples of correct code for this rule:
Promise.resolve()
.then((data) => {
console.log(data);
})
.catch((err) => {
console.error(err);
});Configuration
This rule accepts a configuration object with the following properties:
exceptions
type: string[]
default: []
List of callback function names to allow within Promise then and catch methods.
timeoutsErr
type: boolean
default: false
Boolean as to whether callbacks in timeout functions like setTimeout will err.
How to use
To enable this rule using the config file or in the CLI, you can use:
{
"plugins": ["promise"],
"rules": {
"promise/no-callback-in-promise": "error"
}
}import { defineConfig } from "oxlint";
export default defineConfig({
plugins: ["promise"],
rules: {
"promise/no-callback-in-promise": "error",
},
});oxlint --deny promise/no-callback-in-promise --promise-pluginVersion
This rule was added in v0.10.0.