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
I'm in favor of removing all classes name suffixes in the Acme\Task namespace everywhere it's not inside a Symfony's bundle.
So we would remove "Command", "Event", and so on...
Does it feel weird to keep suffixes in bundles only?
I mean, we don't need them in first-citizen classes, but we obviously need to follow conventions in Symfony related classes. So we'd have mixed naming conventions ;-)
What do you think?
The text was updated successfully, but these errors were encountered:
Hi,
I'm in favor of removing all classes name suffixes in the Acme\Task namespace everywhere it's not inside a Symfony's bundle.
So we would remove "Command", "Event", and so on...
Does it feel weird to keep suffixes in bundles only?
I mean, we don't need them in first-citizen classes, but we obviously need to follow conventions in Symfony related classes. So we'd have mixed naming conventions ;-)
What do you think?
The text was updated successfully, but these errors were encountered: