disposables

disposables

Disposables let you safely compose resource disposal semantics. Think DOM nodes, event handlers, socket connections.

This tiny package includes several disposables:

• Disposable ensures its dispose action runs only once;
• CompositeDisposable ensures a group of disposables are disposed together;
• SerialDisposable switches underlying disposables on the fly and disposes them.

This implementation of disposables is extracted from RxJS. I took the liberty to tweak the code style to my liking and provide this as a standalone package.

The API is mostly the same as RxJS except stricter in a few places. It does not strive for 100% API compatibility with RxJS, but general disposable behavior should match.

It's best if you consult the source and tests, as classes are small and few.

Usage

Importing

import { Disposable, CompositeDisposable, SerialDisposable } from 'disposables';

// or you can import just the ones you need to keep it even tinier
// import SerialDisposable from 'disposables/modules/SerialDisposable';

function attachHandlers(node) {
	let someHandler = ...;
	node.addEventHandler(someHandler);

	// use Disposable to guarantee single execution
	return new Disposable(() => {
	  node.removeEventHandler(someHandler);
	});
}

// CompositeDisposable lets you compose several disposables...
let nodes = ...;
let compositeDisp = new CompositeDisposable(nodes.map(attachHandlers));

// and more later...
let moreNodes = ...
moreNodes.map(attachHandlers).forEach(d => compositeDisp.add(d));

// and dispose them at once!
function goodbye() {
	compositeDisp.dispose();
}

// ... or replace with a bunch of new ones ...
let serialDisp = new SerialDisposable();
serialDisp.setDisposable(compositeDisp);

function replaceNodes(newNodes) {
	let nextCompositeDisp = newNodes.map(attachHandlers);

	// release all the previous disposables:
	serialDisp.setDisposable(nextCompositeDisp);
}

// with a guarantee of each dispose() called only once.

Why Use This Over RxJS

• You only need disposables and not observables;
• RxJS is still figuring out its modularity story and it's not ready.

Really, there are no other reasons.

License

Like the original RxJS code, it is licened under Apache 2.0.