Lowercase or CamelCase namespaces?

rob006 · April 20, 2019, 7:58am

These are only examples. They’re not even recommendations - standard does not say anything about case of namespaces.

sidtj · April 20, 2019, 8:53am

I said they are examples and I didnt say they are recommendations. But to me, the point is that, for some reason, they preffer to use StudlyCaps and they show that in all namespaces of all PSRs. Is not that the place where php devs are looking for examples and recommendations of standards? I think so.

rob006 · April 20, 2019, 9:06am

This is example of consistency. Treating this as an recommendation is just overinterpretation.

sidtj · April 20, 2019, 6:06pm

I am wondering why not consistency examples in lowercase or camelCase. Other vendors probably looked at those consistency examples and realized that all they need is exactly “consistency”, even although it was not a recommendation (till now).

sidtj · April 20, 2019, 6:13pm

Furthermore, if PHP-FIG would decide to make a recommendation about this in some moment, it is easy to see what would be the more consistent choice they would pick.

samdark · April 20, 2019, 9:58pm

Here’s preliminary decision:

github.com

yiisoft/docs/blob/master/004-namespaces.md

# 004 - Namespaces

Package namespace rules are the following:

1. PascalCase is used for namespace parts.
2. Root vendor namespace is `Yiisoft`.
3. Package name parts are used in namespace.


Some examples:

| Package          | Namespace
|------------------|-----------------
| yiisoft/yii-web  | Yiisoft/Yii/Web
| yiisoft/di       | Yiisoft/DI
| yiisoft/db-mysql | Yiisoft/Db/MySQL

Not set in stone yet.

machour · April 21, 2019, 10:58am

If we’re going with yiisoft, I’d rather use YiiSoft if that’s okay with you.

softark · April 21, 2019, 11:34am

Doesn’t it require the package names to be yii-soft/xxx?

machour · April 21, 2019, 11:43am

True that

rob006 · April 22, 2019, 9:24am

They didn’t explained. Maybe there was not reason (they flipped a coin) or reason is no longer valid.

Why Yiisoft/DI and Yiisoft/Db/MySQL instead of Yiisoft/Di and Yiisoft/Db/Mysql?

samdark · April 22, 2019, 8:56pm

Because it makes sense not to lowercase in some cases such as MySQL.

rob006 · April 23, 2019, 9:02am

For me, it does not make sense at all. It just adds another weird rule which is hard to follow. Now you need to think twice what case you should use for this word in a namespace (Is it acronym? Or maybe just weird variation like MySQL or SQLite)? It is all much simpler with strict pascal/camel case, when the case of words is ignored and uppercase letters are used only to indicate word separators. It is also consistent with convention used so far for class names (MysqlMutex instead of MySQLMutex)

samdark · April 23, 2019, 3:06pm

After some practical application I tend to agree.

MysteryDragon · October 8, 2019, 9:19am

Hi everyone!

Well, I’m pretty late to add something valuable to this duscussion, but I still want to share my point of view, because I didn’t see this argument in messages above.

Personally I vote for PascalCase, because of:

It’s common, and in case of using third-party packages “use” section looks more convenient. It’s like a standard now, yes. And that has already been pointed here.
And also, it’s about how do you look at this:
- on the one hand, we start from CLASS naming, like this: This\Is\My\Very\Concrete\Class - so, it’s more for detailed class name
- on the other hand, we start from DIRECTORY naming: here is my “services” folder, which contains several classes (that’s why it’s plural!) including my ConcreteService class, so it’s services\ConcreteService

That’s why I’m also against plural form for PascalCase namespaces and singular form for camelCase ones.