Juan Carlos ANdreu created CB-13173:
---------------------------------------

             Summary: Project's plugin definitions/files when nofetch issue and 
plugins all around the place. Consistency.
                 Key: CB-13173
                 URL: https://issues.apache.org/jira/browse/CB-13173
             Project: Apache Cordova
          Issue Type: Bug
          Components: cordova-cli, cordova-plugins
    Affects Versions: 7.0.1
         Environment: Windows 10, C 7.0.1
            Reporter: Juan Carlos ANdreu
            Priority: Blocker


Hello,

Main issue here is that if I add a plugin with nofetch so it gets it from git 
for example (vla clone), it works as expected initially.  The plugin is not 
added in the project.json dependencies, but just in cordova.plugins:[]. Good. 
But then if any platform is removed and readded, the nofetch plugins are added 
to project.json's dependencies and causes an issue when doing npm install, or 
removing any platform. 

I can see how after adding android platform, it adds the line for 
"cordova-android": "^6.2.3" and then starts to install the plugins specified in 
config.xml. But it goes for all plugins, even those added as nofetch.

So I have to manually remove those plugins by hand.

While doing this I notice that there are too many places where plugins are 
defined. config.xml, project.json dependencies and cordova.plugins:[]

Then they go to ./plugins/fetch and ./plugins/<platform>

Code is downloaded in ./node_modules/<plugin> , ./plugins/<plugin> and 
./platforms/<platform>/

I think cordova needs a bit of consistency , specially in the plugins area.

Why include all plugins everywhere and not in something like 
cordova.plugins.json file? Why not have eveything in that schema, like 
cordova.platforms.json, cordova.config.json etc

That way we can get stuff a bit more organized.

Thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to