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
Why does not it preserve hypens for package name?
It's perfectly valid to have them named like that.
That makes very hard to share packages across projects trough repositories.
Package name should not be used with studly_case, because it removes valid characters.
Use only studly_case for everything else but not there.
Example: php artisan module:make Super-Blog
Should generate name in composer.json as "name": "pingpong-modules/super-blog" not "name": "pingpong-modules/superblog", not to mention other caveats.
And in module.json it should continue using current format "name": "SuperBlog".
Package name does not need to follow any PSR git have their own rules. Do not confuse package name for module name.
The text was updated successfully, but these errors were encountered:
Why does not it preserve hypens for package name?
It's perfectly valid to have them named like that.
That makes very hard to share packages across projects trough repositories.
Package name should not be used with studly_case, because it removes valid characters.
Use only studly_case for everything else but not there.
Example:
php artisan module:make Super-Blog
Should generate name in
composer.json
as"name": "pingpong-modules/super-blog"
not"name": "pingpong-modules/superblog"
, not to mention other caveats.And in
module.json
it should continue using current format"name": "SuperBlog"
.Package name does not need to follow any PSR git have their own rules. Do not confuse package name for module name.
The text was updated successfully, but these errors were encountered: