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
Hitting <return> to accept the default root namespace for a module results in Invalid input.
/var/www/project/cms_v4 $ php craft make module
Module ID: (kebab-case) woof
Module location: [modules/woof]
What should the root namespace for modules/woof/ be?
Invalid input.
What should the root namespace for modules/woof/ be?
Invalid input.
What should the root namespace for modules/woof/ be?
Invalid input.
What should the root namespace for modules/woof/ be?
I'd expect that it would just use what it was offering as a default.
Steps to reproduce
php craft make module
hit <return> when it asks "What should the root namespace for ... be?"
Additional info
n/a
The text was updated successfully, but these errors were encountered:
It’s asking for a root namespace, not a root location.
It will only ask for a root namespace if the default provided location isn’t autoloadable to begin with. In your case that means that you don’t have a preexisting autoload root for modules/ or modules/woof/ yet in composer.json. So a new autoload root will need to be created that points to modules/woof/.
Description
Hitting
<return>
to accept the default root namespace for a module results inInvalid input.
I'd expect that it would just use what it was offering as a default.
Steps to reproduce
php craft make module
<return>
when it asks "What should the root namespace for ... be?"Additional info
n/a
The text was updated successfully, but these errors were encountered: