We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We use numbers in the composer package name, which should be fine: https://getcomposer.org/doc/04-schema.md#name, but is rejected as Invalid input.
Invalid input
Looks like 'pattern' => '/^[a-z][a-z\\-]*\\/[a-z][a-z\\-]*$/', is used, which is too strict.
'pattern' => '/^[a-z][a-z\\-]*\\/[a-z][a-z\\-]*$/',
craft make plugin
wsydney76/testplugin
Composer package name
/ Klara
The text was updated successfully, but these errors were encountered:
Yep, I ran into this, too:
Composer package name: [nystudio/mistletoe] nystudio107/craft-mistletoe Invalid input.
nystudio107 as a company is banned. I feel attacked 😄
nystudio107
Sorry, something went wrong.
ec094e5
Thanks for reporting! 1.0.3 is out now with Composer’s recommended package name pattern.
No branches or pull requests
Description
We use numbers in the composer package name, which should be fine: https://getcomposer.org/doc/04-schema.md#name, but is rejected as
Invalid input
.Looks like
'pattern' => '/^[a-z][a-z\\-]*\\/[a-z][a-z\\-]*$/',
is used, which is too strict.Steps to reproduce
craft make plugin
wsydney76/testplugin
when prompted forComposer package name
Additional info
/ Klara
The text was updated successfully, but these errors were encountered: