Jason Brumwell

Feature timeout handler

3

Adds the ability to use a custom timeout handler, currently we expose TimeoutError but no way to inherit from it and apply it to callbacks as a handler.

Feature async

1

Async should be a feature that is disabled by default, its use cases are for modules that do not follow best practises when creating events or callbacks, which should be...

This will generate a unique id for each callback, useful for when transmitting over network, and also will be vital for the next pull request which will deal with freeing...

This will allow for users to have a rolling timeouts for callbacks that should be called regularly. How `cb.interval(1000)` sets a timeout and has it reset on each iteration `cb.interval(false)`...

Free the callback automatically on timeout, or via the `cb.free()` method from emitters. emitters are added using `cb.emitter(ee);`

Allow for the context of the callback to be changed, also allows currying of arguments. Should close this ticket/PR https://github.com/jmar777/cb/pull/1

Allows for you to retrieve the callback original passed before and after timeout. This makes the callback callable even after timeout.

This PR will allow for a cb timeout to be cleared and not just extended/reduced

In neo4j we would use `WHERE n:LABEL` or `WHERE NOT n:LABEL` this does not seem to be supported in agens, is that expected? As a work around `WHERE label(n) =...

Destructuring results in invalid write reference

4

Given the following code; ``` const { x = 10 } = {}; ``` The result is two write declarations on variable `x` the first to `10` and the second...