... | ... | @@ -103,23 +103,26 @@ class FooBar implements MySimpleInterface { |
|
|
|
|
|
### Naming Conventions
|
|
|
|
|
|
* Use camelCase, not underscores, for variable, arguments, function and method names;
|
|
|
|
|
|
* Use lower underscores for array keys, option names and parameter names;
|
|
|
|
|
|
* Use camelCase, not underscores, for variable, function and method names, arguments;
|
|
|
* Use underscores for array keys, option names and parameter names;
|
|
|
* Use namespaces for all classes;
|
|
|
* Prefix abstract classes with Abstract.
|
|
|
* Suffix interfaces with Interface;
|
|
|
* Suffix traits with Trait;
|
|
|
* Suffix exceptions with Exception;
|
|
|
* Use alphanumeric characters and underscores for file names;
|
|
|
|
|
|
* Prefix abstract classes with Abstract;
|
|
|
|
|
|
* Suffix interfaces with Interface;
|
|
|
|
|
|
* Suffix traits with Trait;
|
|
|
#### Service Naming Conventions
|
|
|
|
|
|
* Suffix exceptions with Exception;
|
|
|
* A service name contains groups, separated by dots;
|
|
|
* The DI alias of the bundle is the first group (e.g. fos_user);
|
|
|
* Use lowercase letters for service and parameter names;
|
|
|
* A group name uses the underscore notation;
|
|
|
* Each service has a corresponding parameter containing the class name, following the SERVICE NAME.class convention.
|
|
|
|
|
|
* Use alphanumeric characters and underscores for file names;
|
|
|
|
|
|
* Don't forget to look at the more verbose Conventions document for more subjective naming considerations.
|
|
|
|
|
|
### Documentation
|
|
|
|
... | ... | |