Hilke Heremans

Just to add, I also believe it would be a useful addition (to both Reader and Writer). I worked around it manually for now by wrapping the nsqjs library.

See PR for what you mentioned here, with some extras. Note that I didn't use object-assign but instead a more generic shim. Might be good to test this shim a...

@jrgleason Try this using bluebird Promises ``` Promise.map(regulation.sources, function(source) { return mergeSourceAsync(source,transaction) },{concurrency:1}).then(function(value) { // commit }).catch(function(error) { // rollback }) ``` Easiest to handle this using async/await or coroutines/yield....

Yes, that's definitely the kicker. It'll make sure every promise is executed _sequentially_. It's great fun :-)

+1 as well, not necessarily because it's ES6 but because it's no longer coffeescript and will open the door to more pull requests (especially from my end, eg for #164...

Not to spoil the party: I could definitely applaud node-neo4j going all out for promises, but aren't there more important things to do when you could just use **bluebird.promisifyAll** which...

@bojidar-bg Maybe I'm missing something, please help me understand the complete issue for you? My take on it: after promisifying it all, you can easily wrap neo4j's Async calls in...

@jrgleason Have you tried bluebird's Promise.map with {concurrency:1} as an option? ``` Promise.map([array_of_values],function(value) { // return a promise }, {concurrency:1}) ``` Promise.map allows you to execute a variable number of...

Would it help if you knew you can declare your events or commands in an array in one file instead of in separate files?

Just to add - if the issue can be verified - I would guess this issue belongs more in `json-schema-ref-parser` than here.