[2.x] Title Length

Thank you for applying!

Please read Review process for security advisory coverage: What to expect → for more details and Security advisory coverage application checklist → to understand what reviewers look for. Tips for ensuring a smooth review → gives some hints for a smoother review.

The important notes are the following.

• If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
• For the time this application is open, only your commits are allowed.
• The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application and no other user will be able to opt projects into security advisory policy.
• We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

To the reviewers

Please read How to review security advisory coverage applications → , Application workflow → , What to cover in an application review → , and Tools to use for reviews → .

The important notes are the following.

• It is preferable to wait for a Code Review Administrator before commenting on newly created applications. Code Review Administrators will do some preliminary checks that are necessary before any change on the project files is suggested.
• Reviewers should show the output of a CLI tool → only once per application.
• It may be best to have the applicant fix things before further review.

For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues → .

I have reviewed code. But I think there is not enough php code to review.

Senior reviewer may review code with this point.

Usually, after reviewing a project, we allow the developer to opt projects into security advisory coverage. This project is too small for us; it doesn't contain enough PHP code to really assess your skills as a developer.

Do you have any other project hosted on drupal.org that we could instead review?

Yes, this module is very small.
@apaderno, I am also the maintainer of the Drupal 10 version of the module https://www.drupal.org/project/title_length → .
Thank you!

1. FILE: src/Commands/TitleLengthCommands.php

$titleLengthService = \Drupal::service($entity_type . '_title_length.' . $entity_type);

\Drupal calls should be avoided in classes, use dependency injection instead

2. FILE: src/EntityTitleLength.php

  /**
   * Constructor of EntityTitleLength class.
   *
   * @param \Drupal\Core\Database\Connection $connection
   *   Database connection.
   * @param \Drupal\Core\Entity\EntityTypeManagerInterface $entity_type_manager
   *   Entity type manager.
   * @param \Drupal\Core\Entity\EntityDefinitionUpdateManager $update_manager
   *   Update Manager.
   */
  public function __construct(Connection $connection, EntityTypeManagerInterface $entity_type_manager, EntityDefinitionUpdateManager $update_manager) {

The documentation comment for constructors is not mandatory anymore, If it is given, the description must be Constructs a new [class name] object. where [class name] includes the class namespace.

3. FILE: modules/node_title_length/node_title_length.info.yml

core_version_requirement: ^8 || ^9 || ^10

FILE: modules/taxonomy_term_title_length/taxonomy_term_title_length.info.yml

core_version_requirement: ^8 || ^9 || ^10

The Drupal Core versions before 8.7.7 do not recognize the core_version_requirement: key.