You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
Creating a new module still requires the user to do a composer update for PSR-4 namespaces to be added to Composer. A nice prompt informing the user of this, after the module creation is completed, would be nice.
If composer update is not done, the new ConfigProvider.php is not found.
The text was updated successfully, but these errors were encountered:
Hmm... enabling the module is delegated to logic in zf-composer-autoloading, which, as part of its work, calls on composer dump-autoload. When I've run this on Linux systems, it's "just worked"; autoloading is setup and ready to use immediately after running the module:create command.
Have you tried passing the --composer/-c option to specify the path to the composer command? If not, could you try that, and let me know if that causes autoloading to work?
Creating a new module still requires the user to do a
composer update
for PSR-4 namespaces to be added to Composer. A nice prompt informing the user of this, after the module creation is completed, would be nice.If
composer update
is not done, the newConfigProvider.php
is not found.The text was updated successfully, but these errors were encountered: