

AsyncResolver.js: Resolve async subscribed decisions
source link: https://www.tuicool.com/articles/hit/eMBnUv6
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

async-resolver
AsyncResolver.js implements a PubSub architecture where subscribers of events are decision makers (return promise when they receive an event) and after publishing an event, publisher gets the decision of the subscribers. Supports both Node and browser.
Where to use?
There are situations where we want to maintain distinct subscribers of an event, though want to act on the basis of how subscribers react. AsyncResolver.js is the solution for this need, it's an amalgamation of pub sub architecture and promises to provide decision making capability in asynchronous environment.
For example: Let's consider a case where there are several components on a webpage, whose state can be changed by the user and we make every component to subscribe as listener to listen to a page transition so that we can check if a user is trying to move without saving data.
Now, when an individual clicks on a link, we publish an event mentioning of the transition of the user from the page, though we want to ask every listener (or component) if user has made any changes to their state and is moving without saving them. In case there are any unsaved changes in any of the component, then we cancel the transition and instead dispay an information dialog to the user asking him to save information before proceeding further.
Install
### NPM npm install async-resolver ### Yarn yarn add async-resolver
Usage
const AsyncResolver = require('async-resolver'); let resolver = new AsyncResolver(); resolver.subscribe('locationChange', () => { // custom logic return Promise.resolve(); }); resolver.subscribe('locationChange', () => { // custom logic return Promise.reject(); }); resolver .publish('locationChange', { promiseMethod: 'any' }) .then(() => console.log('location change allowed')) .catch(() => console.log('location change denied'))
API
AsyncResolver()
Returns AsyncResolver
function that can be instantiated.
subscribe(eventName, callback)
Allows subscribing to the event and executing the callback when an event is published.
eventName
Type: string
Event published.
callback
Type: function
Callback to be executed when the publish event is received.
publish(eventName, options)
Returns a promise, that defines the decision of subscribers.
eventName
Type: string
Event published.
options
Type: object
Options to be passed while publishing to an event.
options.promiseMethod
Type: string
Method to be applied at the collection of promises such as all
, any
etc. Here's list of methods supported by Promise collection.
License
MIT © Apoorv Saxena
Recommend
-
44
More than 2 months passed since myprevious review of active MySQL bug reports I am subscribed to, so it's time to describe what I was interested in this summer. Let's start with few bug reports that really surp...
-
45
I've subscribed to more than 60 new bug reports since myprevious post in this series. It means that I'd need 4-5 posts to cover all new subscriptions and reasons behind them. I still plan to write about most of the bug r...
-
43
It's time to continue my review of MySQL bug reports that I considered interesting for some reason recently. I had not got any notable reaction from Oracle engineers to myprevious post about recent regression bugs in MyS...
-
54
For some reason the Committee of FOSDEM 2019 MySQL, MariaDB & Friends Devroom of all my talks submitted picked up the one on how to create a useful MySQL bug report, so I...
-
78
Holidays season is almost over here, so it's time to get back to my main topic of MySQL bugs. Proper MySQL bug reporting will be a topic of my FOSDEM 201...
-
63
Slides for my talk about MySQL bugs at FOSDEM 2019 MySQL, MariaDB and Fr...
-
44
More than 3 weeks passed since myprevious review of public MySQL bug reports I am subscribed to, so it's time to present some of the bugs I've considered interesting in January, 2019. As usual, I'll review them...
-
54
Today I'd like to continuemy review of public MySQL bug reports with a list of some bugs I've subscribed to over last 3 weeks. It's already long enough and includes nice cases to check and share. Note that I usually subs...
-
61
I have not much yet to say on a popular topic of
-
11
HomeProductivityI subscribed to Seth Godin’s Blog, and Now I’m a Blogger Again I subscribed to Seth Godin’s Blog, and Now I’m a Blog...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK