With the last cordova versions the plugins configurations are removed from config.xml and set in package.json. Then this plugin can work correctly if get the incorrect list of plugins.
The changes proposed will read the cordova plugins in package.json, then search the url in dependencies and devDependencies and compare like in config.xml
With scoped plugins, the devDependencies name doesn't have the same name, what it's inside cordova.plugins.
@havesource/cordova-plugin-push --> havesource-cordova-plugin-push
To compare I check that the same url exists with the plugin in fetch.json then the plugins is installed.
[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation changes
[ ] Other... Please describe:
PR Checklist
For bug fixes / features, please check if your PR fulfills the following requirements:
[ ] Testing has been carried out for the changes have been added
[ ] Regression testing has been carried out for existing functionality
[ ] Docs have been added / updated
What is the purpose of this PR?
Does this PR introduce a breaking change?
[ ] Yes
[X] No
What testing has been done on the changes in the PR?
Executed with --target=config and --target=package return the same results in different projects.
What testing has been done on existing functionality?
PR Type
What kind of change does this PR introduce?
With the last cordova versions the plugins configurations are removed from config.xml and set in package.json. Then this plugin can work correctly if get the incorrect list of plugins.
The changes proposed will read the cordova plugins in package.json, then search the url in dependencies and devDependencies and compare like in config.xml
With scoped plugins, the devDependencies name doesn't have the same name, what it's inside cordova.plugins. @havesource/cordova-plugin-push --> havesource-cordova-plugin-push To compare I check that the same url exists with the plugin in fetch.json then the plugins is installed.
PR Checklist
For bug fixes / features, please check if your PR fulfills the following requirements:
What is the purpose of this PR?
Does this PR introduce a breaking change?
What testing has been done on the changes in the PR?
Executed with --target=config and --target=package return the same results in different projects.
What testing has been done on existing functionality?
Other information