[ 
https://issues.apache.org/jira/browse/CB-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shazron Abdullah updated CB-6458:
---------------------------------
    Labels: config.xml  (was: config.xml cordova-ios-5.0.x)

> 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
>          Components: cordova-cli
>         Environment: config.xml
>            Reporter: Shazron Abdullah
>            Priority: Minor
>              Labels: config.xml
>             Fix For: cordova-ios@5.0.0
>
>
> 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to