[
https://issues.apache.org/jira/browse/CB-9065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556888#comment-14556888
]
ASF GitHub Bot commented on CB-9065:
------------------------------------
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104784245
So, I discussed this a bit with Steve, and he brought up an interesting
point.
A stretch goal is to not have a plugin.xml file at all, and simply use
package.json for the entire plugin definition.
Given that the `<name>` tag only exists in plugin.xml, could be removed,
and is not unique ( which I see you handle ) does it still make sense to push
users to rely on a convenience function that we may end up removing? The name
property in a package.json IS the id.
Potentially we could also add a cordova.name field to package.json
> Allow removing plugins by short name
> ------------------------------------
>
> Key: CB-9065
> URL: https://issues.apache.org/jira/browse/CB-9065
> Project: Apache Cordova
> Issue Type: Improvement
> Affects Versions: 5.0.0
> Reporter: Tim Barham
> Assignee: Tim Barham
>
> It would be nice if we could remove plugins by short name. Things are better
> now with the new plugin ids - it's easier to remember and type {{cordova
> plugin remove cordova-plugin-camera}} than {{cordova plugin remove
> org.apache.cordova.camera}}, but it would be even nicer to only have to type
> {{cordova plugin remove camera}}.
> If multiple installed plugins happen to share the same short name, the remove
> command should probably just fail (with an informative error message).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
