Think of how Rails, e.g. allows you to define a property as associated with another:
class Customer < ActiveRecord::Base
has_many :orders
end
The get
and set
function keywords seem to be incompatible with the async
keyword. However, since async
/await
is just a wrapper around Promise
s, you can just use a Promise
to make your functions "await
-able".
Note: It should be possible to use the Object.defineProperty
method to assign an async
function to a setter or getter.
Promises work well with getters.
Here, I'm using the Node.js 8 builtin util.promisify()
function that converts a node style callback ("nodeback") to a Promise
in a single line. This makes it very easy to write an await
-able getter.
var util = require('util');
class Foo {
get orders() {
return util.promisify(db.find)("orders", {customer: this.name});
}
};
// We can't use await outside of an async function
(async function() {
var bar = new Foo();
bar.name = 'John'; // Since getters cannot take arguments
console.log(await bar.orders);
})();
For setters, it gets a little weird.
You can of course pass a Promise to a setter as an argument and do whatever inside, whether you wait for the Promise to be fulfilled or not.
However, I imagine a more useful use-case (the one that brought me here!) would be to use to the setter and then await
ing that operation to be completed in whatever context the setter was used from. This unfortunately is not possible as the return value from the setter function is discarded.
function makePromise(delay, val) {
return new Promise(resolve => {
setTimeout(() => resolve(val), delay);
});
}
class SetTest {
set foo(p) {
return p.then(function(val) {
// Do something with val that takes time
return makePromise(2000, val);
}).then(console.log);
}
};
var bar = new SetTest();
var promisedValue = makePromise(1000, 'Foo');
(async function() {
await (bar.foo = promisedValue);
console.log('Done!');
})();
In this example, the Done!
is printed to the console after 1
second and the Foo
is printed 2
seconds after that. This is because the await
is waiting for promisedValue
to be fulfilled and it never sees the Promise
used/generated inside the setter.