Consider allowing jagged options parameters

[yavorg]

Today if I want to send just some of the parameters using the parametrized method signature, not the object, I am tempted to set the parameters I don't want to 'null' or 'undefined'.

mpns.sendFlipTile(pushUri, null, 5, 'amazing');

This will result in an error because null tests as typeof == 'object' and our current logic will assume I'm using the options object method signature. I suspect lots of folks will be bitten by this and get confused.