I mentioned in #129 that it would be useful to add a Composer dependency for the wxPHP code completion file. I expect it'd use the dev-only approach, so that it is not added to live envs. It should prove useful for users who are lucky enough to have the extension available in their distro's repository, and so they don't need to clone the wxphp repo or run the generation script.
This feature might have the small additional benefit of getting more users to be aware of wxPHP, since it will be visible on Packagist.
Do you foresee any issues with this? It'd just be a copy of the latest generated file, pegged to the version number of wxPHP (perhaps with an additional version number to allow for improvements in the generated output).
I'd need to learn how to set up the composer.json file suitable for Packagist, but it can't be too hard...
I mentioned in #129 that it would be useful to add a Composer dependency for the wxPHP code completion file. I expect it'd use the dev-only approach, so that it is not added to live envs. It should prove useful for users who are lucky enough to have the extension available in their distro's repository, and so they don't need to clone the
wxphprepo or run the generation script.This feature might have the small additional benefit of getting more users to be aware of wxPHP, since it will be visible on Packagist.
Do you foresee any issues with this? It'd just be a copy of the latest generated file, pegged to the version number of wxPHP (perhaps with an additional version number to allow for improvements in the generated output).
I'd need to learn how to set up the
composer.jsonfile suitable for Packagist, but it can't be too hard...