Fixes an issue of args === undefined and script terminates

[yallups]

I am returning false on select2:opening and I get this error for args being undefined. it terminates execution and breaks other things.

in this patch the functionality remains without breaking execution.

I tried being explicit in the code convention but this could also be a small footprint with
A:

args || (args = {});

B:

args === undefined && (args = {});

[yallups]

I have this work around at the moment
https://gist.github.com/yallups/ea797dceaa2c18898554

[yallups]

Just found the issue that this fixes. #3431
I know that @kevin-brown wants to make sure to always pass an empty object as an argument but I have a feeling that this will keep coming back. If the function is dependent on having an object with a property then we should make sure we have one and it shouldn't be the responsibility of the caller. (IMO ;))

[kevin-brown]

I tried being explicit in the code convention

I'd much rather have the code be explicit in this case, so the current way is fine.

I know that @kevin-brown wants to make sure to always pass an empty object as an argument but I have a feeling that this will keep coming back.

The main reason for framing this as a "let's fix the missing object" issue instead of a "let's prevent this going further" was because I'd rather favor explicitly passing in no extra parameters when raising an event than having that handled implicitly. That's within the core codebase though, which is something we control, and it's not something we can expect for third-party plugins and adapters.

So yeah, this PR seems reasonable.

[yallups]

Thanks for the merge!
I see your point about being explicit in the method call though.