[
https://issues.apache.org/jira/browse/CB-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971830#comment-13971830
]
Andrew Grieve commented on CB-6458:
-----------------------------------
That's true. I think they need more thought as well though. E.g. you can't set
a variable for a dependent plugin, you can't change the value of a variable
post-install, they aren't remembered when installing into a new platform. If
it's a value from the user that you want, then <preference> just works better
right now.
> Support reading of <feature> param values other than "onload" and "x-package"
> keys
> ----------------------------------------------------------------------------------
>
> Key: CB-6458
> URL: https://issues.apache.org/jira/browse/CB-6458
> Project: Apache Cordova
> Issue Type: Bug
> Environment: config.xml
> Reporter: Shazron Abdullah
> Priority: Minor
>
> There is no component for this, this relates to config.xml.
> For the proposed solution, there are no changes needed to the config.xml
> specification, since the feature tag already supports param child tags.
> I'm only speaking for iOS, not sure about the other platforms.
> The problem is, there is no access to these additional values in plugin code.
> The plugin has to re-read the config.xml to access this.
> What are the alternatives in config.xml/plugin.xml?
> 1. preference tag on the plugin level
> 2. preference tag on the platform level
> The problem with either of these two approaches is that if another plugin has
> the same key, it will clobber your preference. The ugly solution to that is,
> to namespace your key with your feature name as a prefix.
> Proposed solutions:
> 1. Create a plugin in cordova-labs to read these extra param values without
> touching the core code.
> 2. Modify the core code to read these extra param values, and expose them to
> the user
--
This message was sent by Atlassian JIRA
(v6.2#6252)
