Currently, I am developing a node application that heavily utilizes promises. To enhance the readability of my code, I have been removing anonymous functions and storing them in a JavaScript object called "myCallbacks". Here's an example:
let myCallbacks = {
myFirstCallback: function(fulfill, reject) {
// Perform certain tasks
if(noError)
fulfill({field: 'data'});
else
reject('ERROR');
},
mySecondCallback: function(fulfill, reject) {
// Perform certain tasks
if(noError)
fulfill({field: 'data'});
else
reject('ERROR');
}
}
let myFirstMethod = function() {
return new Promise(myCallbacks.myFirstCallback);
}
let mySecondMethod = function() {
return new Promise(myCallbacks.mySecondCallback);
}
This approach has proven to be effective.
Now, I encountered a situation where I need to pass data to my callbacks. Let me provide you with an example:
let myCallbacks = {
myFirstCallback: function(fulfill, reject) {
// Perform certain tasks
if(noError)
fulfill({field: 'data'});
else
reject('ERROR');
},
mySecondCallback: function(fulfill, reject) {
// Perform certain tasks
if(noError)
fulfill({field: 'data'});
else
reject('ERROR');
},
myThirdCallback: function(fulfill, reject, someVariable) {
// Perform certain tasks
if(someVariable*3>10)
fulfill({field: 'data'});
else
reject('ERROR');
}
}
let myFirstMethod = function() {
return new Promise(myCallbacks.myFirstCallback);
}
let mySecondMethod = function() {
return new Promise(myCallbacks.mySecondCallback);
}
let myThirdMethod = function(someVariable) {
// This approach doesn't work
return new Promise(myCallbacks.myThirdCallback);
// This approach doesn't work either
return new Promise(myCallbacks.myThirdCallback(fulfill, reject, someVariable));
// Nor does this approach work
return new Promise(myCallbacks.myThirdCallback(someVariable));
}
What is the correct way to pass "someVariable" from "myThirdMethod" to "myCallbacks.myThirdCallback()"?