Naming Interfaces - To (pre- / suf)fix or not to fix about php-ddd HOT 8 OPEN

I recently wrote a blog post about this: https://www.alainschlesser.com/interface-naming-conventions/

TL;DR:
Interface suffix (or prefix) is an unnecessary form of Hungarian Notation, and actually severely limits your architecture (by making it impossible to replace classes with interfaces later on, because their nature is encoded in their name). This forces you to proactively put interfaces everywhere to not cause a lock-in to a specific architecture.

from php-ddd.

For long time I've agreed with prefix/suffix like in Symfony or PSR naming conventions but recently I've changed my mind and I think exactly like @schlessera. You don't need to put Interface in name because there IS information that this is interface (the same goes for traits). IDE will display it too. The only thing I accept now is Abstract prefix for abstract classes, but I think it's possible I'll drop it too.

You don't introduce yourself JohnName SmithSurname ;-)

from php-ddd.

Upcoming PHP BC Break: PSR and all frameworks will remove Interface suffix and Abstract prefix from their naming conventions by default.

...Couldn't wait until April fools!

from php-ddd.

But PSR-8 doesn't use Interface suffix.

from php-ddd.

Hey @webdevilopers,

I personally go with the Symfony naming scheme aka ClientInterface.

from php-ddd.

Generally - even in your Domain Model namespace? Or just inside the bundles?

from php-ddd.

I drop the Interface and place all interfaces inside Contracts directory.

from php-ddd.

There is topic on PHP-FIG mailing group about changing conventions in PSRs (only future ones), but it's dead without conclusion.

Nobody expects such BC break, but for any new software it's not the only way of naming.

from php-ddd.