[
https://issues.apache.org/jira/browse/CB-9248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605939#comment-14605939
]
Rob Paveza commented on CB-9248:
--------------------------------
This would be a bad bug to take. Fixes should be preferred to take to plugins,
such that either they silently fail (or just return non-fatal errors), or they
support feature detection so that you can choose to not call the failing API at
runtime because it isn't present.
If we did what you propose, then plugins may get updated, but you might never
update your app to do a particular thing because the plugin is always hidden
behind the platform element, so you never see that its functionality lights up.
> In config.xml, <plugin> inside <platform> is not supported
> -----------------------------------------------------------
>
> Key: CB-9248
> URL: https://issues.apache.org/jira/browse/CB-9248
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, CordovaLib
> Affects Versions: 5.1.2
> Reporter: Leroy van Engelen
> Assignee: Rob Paveza
>
> In config.xml it is possible to define plugins that should be installed using
> the <plugin> tag. Some plugins are not available or are buggy on certain
> platforms. Therefore we need to include them depending on the platform. I
> would expect this to be possible by wrapping them in <platform> tags, but
> these are ignored.
> The problem is that in `cordova-lib/src/configparser/ConfigParser.js` the
> methods `getPluginIdList` and `getPlugin` only top level <plugin> definitions
> are taken into account.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
