"value":"\n <p>When writing code, it's common to suffix the class name with the type of class it is.<\/p>\n\n<p>I do this often for most types of classes, such as Controllers, EventListeners, Factories, Repositories and Builders.<\/p>\n\n<p>However, I don't always for value objects and data transfer objects (DTOs).<\/p>\n\n<p>Also, I don't always suffix interfaces with <code>Interface<\/code>.<\/p>\n\n<p>I've been re-reading the documentation for the Symfony Serializer component, which references both <code>NameConverterInterface<\/code> and <code>MyDto::class<\/code>.<\/p>\n\n<p>Whilst it does make the names more verbose, it does clarify what the class is used for.<\/p>\n\n<p>Symfony's coding standards and Drupal's PHP coding standards have conventions for this, but what do you think?<\/p>\n\n<p>Do you add suffixes to your class or interface names, or do you prefer the simplified versions?<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>When writing code, it's common to suffix the class name with the type of class it is.<\/p>\n\n<p>I do this often for most types of classes, such as Controllers, EventListeners, Factories, Repositories and Builders.<\/p>\n\n<p>However, I don't always for value objects and data transfer objects (DTOs).<\/p>\n\n<p>Also, I don't always suffix interfaces with <code>Interface<\/code>.<\/p>\n\n<p>I've been re-reading the documentation for the Symfony Serializer component, which references both <code>NameConverterInterface<\/code> and <code>MyDto::class<\/code>.<\/p>\n\n<p>Whilst it does make the names more verbose, it does clarify what the class is used for.<\/p>\n\n<p>Symfony's coding standards and Drupal's PHP coding standards have conventions for this, but what do you think?<\/p>\n\n<p>Do you add suffixes to your class or interface names, or do you prefer the simplified versions?<\/p>\n\n ",