You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Darryl Pogue (JIRA)" <ji...@apache.org> on 2018/05/05 07:03:00 UTC

[jira] [Updated] (CB-11963) Get rid of fetch.json and in plugins folders

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

Darryl Pogue updated CB-11963:
------------------------------
    Component/s:     (was: AllPlugins)
                 cordova-plugman
                 cordova-lib
                 cordova-fetch

> Get rid of fetch.json and <platform.json> in plugins folders
> ------------------------------------------------------------
>
>                 Key: CB-11963
>                 URL: https://issues.apache.org/jira/browse/CB-11963
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-fetch, cordova-lib, cordova-plugman
>            Reporter: Philipp Kursawe
>            Priority: Major
>
> In a cordova project you define the plugins in config.xml which kind of serves as the project file.
> Since some time now it also contains the plugins the project is using.
> I wonder why there is still a /plugins/fetch.json and a /plugins/PLATFORM.json for each installed platform. 
> Both somehow list plugins in a redundant way, since the same information is already in config.xml
> More so, the platform JSON contains PACKAGE_NAME that references to the config.xml widget id. Why? Its not like we can have multiple app IDs specified.
> I propose to get rid of those files and make `cordova prepare` actually updating the VARIABLES defined in config.xml plugins. Because at the moment the only way to CHANGE a var in config.xml and see this change being reflected in the built app is to remove the platform and re-add it.
> This is so error prone.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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