[
https://issues.apache.org/jira/browse/CB-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259759#comment-13259759
]
Filip Maj commented on CB-298:
------------------------------
Hey all,
I'd like to resolve this one. I think we all agree that deprecating these
globals is in our best interest. So far the only thing brought up has been
"performance impact" which I am not convinced is a big deal in this case (but
please post bench results if you have data proving otherwise). Really, only
plugins would be affected by this as the cordova APIs all route through the
{{cordova}} object.
@Pat, re:a single call to a console.log for a dep. warning, is that good
enough? Isn't the point of a deprecation warning to be annoying and visible
enough to a user so that (s)he makes recommended changes to their code.
> DEPRECATE "plugins" and "PhoneGap" global objects in JavaScript implementation
> ------------------------------------------------------------------------------
>
> Key: CB-298
> URL: https://issues.apache.org/jira/browse/CB-298
> Project: Apache Callback
> Issue Type: Improvement
> Components: CordovaJS
> Affects Versions: 1.4.0, 1.5.0, 1.6.0
> Reporter: Filip Maj
> Assignee: Simon MacDonald
> Priority: Minor
> Labels: api-change, javascript
> Fix For: 1.7.0
>
>
> There are two globals currently defined in Cordova-JS' common platform
> definition, which get dropped onto the `window` object: `plugins` and
> `PhoneGap`.
> Let's slate these for removal.
> In 1.6, let's set up deprecation notices for these.
--
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
