Why put repositories config into extra about composer-asset-plugin HOT 5 CLOSED

@nsams Because it's not a choice but a constraint.

For extra.asset-repositories: Composer checks the type of vcs repository before the loading of plugins, so, an exception is thrown. The only way, is to put the config in extra section, and I do not like it (see the doc).

For extra.asset-registry-options: This is not the Registry that is deactivable, but only the search for the command "search". This is a preparatory work to add research in the NPM Registry (#6). Given the need to download a file 8MB each time, because there is no API of search for the NPM Registry, this feature is disabled by default (see the doc).

from composer-asset-plugin.

I see, thanks for the reply.

extra.asset-repositories: makes sense. Probably composer could ignore unknown types?

from composer-asset-plugin.

@nsams That is unfortunately not the case...

from composer-asset-plugin.

well, it could be another pull request that changes that :D

from composer-asset-plugin.

If you get to do the PR and convince @Seldaek and @naderman to merge your PR in Composer, I will be my pleasure to change the registering of the asset vcs repositories.

from composer-asset-plugin.