If its dependant is removed, it will stop working anyway -- so why is it a bug to remove it?
I think we should warn when this happens (if it happens silently, thats bad experience), or better yet prompt for input to confirm removal, but I'm not sure what it would mean to just leave pluginA installed when its dependant is removed, regardless of if each plugin was explicitly installed. -Michal On Wed, Mar 12, 2014 at 12:58 PM, Shazron <[email protected]> wrote: > Just tested it with File and File-Transfer - looks like a bug. Please file > it, thanks! > > > On Wed, Mar 12, 2014 at 7:46 AM, Li, Jonathan <[email protected]> wrote: > > > When testing with cordova 3.4.0-0.1.3, if a plugin A is a dependent of > > plugin B, then running the following command will automatically delete > > plugin B from the project > > > > cordova plugin add PluginB > > cordova plugin add pluginA > > cordova plugin rm pluginB > > > > As pluginA is explicitly added into the project, unless it is explicated > > removed from project by using "cordova plugin rm pluginA" command, then > it > > should not be deleted from the project when deleting pluginB. > > > > The test is done on iOS platform. > > > > Please let me know if this is a known issue, or whether I need to submit > a > > bug for it > > > > Thanks > > Jonathan > > > > > > >
