[
https://issues.apache.org/jira/browse/CB-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224517#comment-13224517
]
Filip Maj commented on CB-255:
------------------------------
First, for 1.6 and maybe a couple of point releases following it, we're aiming
for full cordova-js integration and so let's move to the common approach of
using just the arguments array.
That being said, I like the named parameter approach (I think it is clearer).
After cordova-js is integrated into more platforms, I think we can open an
issue in changing the parameterization approach.
Second, specific to this issue, definitely need to fix the missing "null" for,
at the minimum for 1.6 as cordova-js lands in iOS.
> iOS: a parameter with value 'null' is not passed to 'arguments' array
> ----------------------------------------------------------------------
>
> Key: CB-255
> URL: https://issues.apache.org/jira/browse/CB-255
> Project: Apache Callback
> Issue Type: Bug
> Components: CordovaJS, iOS
> Affects Versions: 1.4.0
> Environment: iOS Mac OS X 10.7
> Reporter: Oleg Gryb
> Assignee: Shazron Abdullah
> Fix For: 1.6.0
>
>
> In the following JS call the second parameter (null) will not be passed to
> 'arguments' array in a Objective-C controller.
> The 'arguments' array will contain only first ('1') and third ('3')
> parameters.
>
> return PhoneGap.exec(successCallback,
> failureCallback,
> VPCLASS,
> 'method',
> [1, null, 3]);
> Hint: typeof(null) is equal to 'object' in JS. PhoneGap.js uses this check to
> determine if a parameter should go to 'arguments' or to 'options'
> collections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
