It is no doubt that a world without principles and standards, would be a very scary place, because people wouldn’t be expected to perform to a level that is acceptable by others, when they do their jobs.
Imagine for example, if you wait for a red light to turn green, and you are in a country where they don’t take traffic light too seriously. You could bear to wait there for two or maybe even three minutes, but if you wait for more than thirty minutes, then you will notice that there is something wrong with the picture. So what do you do at that point, do you break the law, or do you wait for a light, that you know will not change, before you go?
In today’s article we are going to continue our conversation about Drupal on coding standards, and how you can improve your level of programming, if you learn to adhere to standards set by the Drupal community. Object-oriented programming (OOP) has become a large part of Drupal 8, which has introduced a lot of coding standards for the Drupal developer.
When developers want to organize their code to be more efficient, then they can choose to write their code in OOP, to use the best features that PHP has to offer today. Procedural programming does not give developers the ability to reuse their code, in the form of objects, which can be created or instantiated and contain properties that hold data, and methods that execute function.
Drupal only allow for one class per file, when declaring classes in OOP, the file name should be the same as the name of the class. In Drupal 8 there is a new feature known as PSR4 autoloader, which allow classes to be loaded on demand and automatically, but the naming convention should be followed.
A long list of required statements is not necessary due to autoloading, because classes are named based on the PSR-4 namespacing convention and are used on demand due to the autoloading system. The naming of the classes and how files and directories are arranged is what really matters, for the PSR-4 autoloader to work properly.
If you want your module to be autoloaded properly, you should follow this directory structure, according to drupilize.me. <modulename>/src/<namespace>. This file would contain a list of classes that are used, and inside the file the same coding standards should be follow, as far as spacing and indenting is concerned.
When naming classes, certain basics must be cover, for example, UpperCamel must be used when declaring a class or interface. lowerCamel can be used when declaring a method or a class property, the word “Drupal” or “class” should not be used to name classes. In Drupal, interfaces are used often, to keep the code flexible, because it allows developers to swap classes out for another, at some point in the future of their development if it’s necessary of course.
Developers use interfaces because they are flexible and allow them to implement different functionality, while sharing a common interface, this is known as polymorphism a OOP concept. Classes can be public, private or protected, to declare their visibility, which is a requirement.
Thank you for reading this article!!!