breautek
commented
2 years ago Personally I'd support this kind of feature, but I don't know if overloading the --variable is a good idea for this. I think it may be best to keep that reserved for actual plugin variables.
I think it may better to introduce a new --platforms argument. But I do understand the motivation of reusing the --variable flag, as it would allow restoration to work easily because it would be compatible with the current package.json structure that cordova uses.
To solve the restoration issue, the --platforms argument will require a more extensible cordova structure in it's package.json. Which I think is doable but would likely require a series of PRs before a PR can be made to tackle this issue. This obviously requires a bit extra work but I think is worth it for a cleaner API. It's always easy to add something, but difficult to remove or change.
Interested in hearing your thoughts on this.
It is impossible to do it without manual intervention right now. The only way is to add plugin and then delete specific folders and files which is quite cumbersome and highly repetitive.
Just to add another work around. The plugin could always be forked and have it's platform implementation removed (even just from it's plugin.xml entry) and that should be sufficient to use a plugin and omit one platform's implementation. The drawback of course is that you'd have to manage the fork and periodically pull in updates from upstream and deal with merge conflicts.
ardabeyazoglu
cklam
NikitaKA
Feature Request
I want to add some plugins to only single platform or skip for a certain platform. I already found a way to implement this, and I am willing to develop this feature and send a pull request if approved.
Motivation Behind Feature
Multi platform apps do not always require same functionality. For example, I may have a client who needs nfc features and use only android devices, whereas ios clients don't need them. Besides, one may prefer not to add some specific functionality to each platform although device supports it. So why not just add the plugin and don't implement the feature ? Short answer: to avoid unnecessary approval trouble. For example; If I add phonegap-nfc plugin, the apple approval team see that I am using nfc and ask me to prove how I use it and why I use it ? It is very hard to show what you don't implement and the apple team will not approve it until they see a convincing explanation / proof. The issue becomes especially important when developing ad-hoc apps for customers instead of product apps that are usually same across platforms.
Feature Description
It can be implemented using cli variables that are already built in. A global variable, non conflicting variable such as "cordova-platform" can be used:
cordova plugin add some-cordova-plugin --variable cordova-platform=androidcordova plugin add some-cordova-plugin --variable cordova-platform=android,browserThe command skips install steps for unspecified platforms and save preference to config.xml, so that when a platform is added/removed it can repeat the same behaviour.
Alternatives or Workarounds
It is impossible to do it without manual intervention right now. The only way is to add plugin and then delete specific folders and files which is quite cumbersome and highly repetitive.