promise/no-multiple-resolved Suspicious
What it does
This rule warns of paths that resolve multiple times in executor functions that Promise constructors.
Why is this bad?
Multiple resolve/reject calls:
- Violate the Promise/A+ specification
- Have no effect on the Promise's behavior
- Make the code's intent unclear
- May indicate logical errors in the implementation
Examples
Examples of incorrect code for this rule:
javascript
new Promise((resolve, reject) => {
fn((error, value) => {
if (error) {
reject(error);
}
resolve(value); // Both `reject` and `resolve` may be called.
});
});Examples of correct code for this rule:
javascript
new Promise((resolve, reject) => {
fn((error, value) => {
if (error) {
reject(error);
} else {
resolve(value);
}
});
});How to use
To enable this rule in the CLI or using the config file, you can use:
bash
oxlint --deny promise/no-multiple-resolved --promise-pluginjson
{
"plugins": ["promise"],
"rules": {
"promise/no-multiple-resolved": "error"
}
}