Commit with no function causes it to blow up

[jrgleason]

I have code that uses transactions. It adds a bunch of nodes, however, when everything is done there are no side effects so I tried the following..

transaction.commit();

This blows up saying the function is undefined but this...

transaction.commit(function(){});

Works fine, maybe we should use a quick null check to see if it needs called.

[aseemk]

Sorry for the delay here, but good point — thanks for filing.

I hear you that we could simply check if the function is given first. But I think it's best practice to always require a callback (and not to send a no-op one), in case there are any errors.

So maybe it'd be better for us to check for and require a callback right away?