Vendor Namespace and Package Name should be StudlyCased in the namespace about laravel-packager

[deweller]

I guess the problem is that there is no way to generate both a lowercase directory name with a corresponding StudlyCased namespace. I have to manually edit the namespace in all the generated files.

The nice thing to have here would be the ability to specify the directory name and the namespace separately (with sane defaults).

[Jeroen-G]

I have seen Laravel packages work without studlycases. It is not programmatically required, and that is why I leave it up to you to define the capitals. Or at least it was that way when I designed Packager. That is also why all examples in the readme have capitals.

[Jeroen-G]

Changing the directory to lowercase would only require changing the app composer.json I think.

However, I would accept a PR that fixes this.

[Jeroen-G]

Closed, waiting for Pull Request.

[judgej]

The namespace may be StudyCap cased, but the vendor name and package name and their directories should be lower case. You can call the directories whatever you like in the packages directory, but the convention for composer is a lower case vendor (e.g. "laraval") and lower case package name (e.g. "framework").

Namespaces and vendor/package names, are two completely different things. For example, the "laravel/framework" vendor/package name provides the "\Illuminate" namespace.

[Jeroen-G]

I would welcome a Pull Request.

[omitobi]

I was trying this package today 17th November, 2018 and I seriously couldn't create a package with - between the names and also when I use lower case it doesn't change the namespace to use UpperCase. Its a great job done to provide this package but this issue is quite annoying as I had to change the name of my package to StudlyCase.

[Jeroen-G]

And still no one makes a PR.