[2.x] ImageLightbox

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 → .

For these applications, we need a project where, in at least the branch used for the application, most of the commits (if not all the commits) have been done from the person who applied.

The purpose of these applications is reviewing a project to understand what the person who applies understands about writing secure code that follows the Drupal coding standards and correctly uses the Drupal API. We do not review a project to understand what the project maintainers as a group understands about those topics.

This application can only continue with another project where most of the commits (and preferable all the commits) have been done by the
piridium.

I understand the consideration that the review process aims to understand the competencies of the applicant. However, solely focusing on the commit count strikes me as somewhat superficial. For the past 28 months, nearly all commits have been made by the applicant, and during this time, a significant portion of the module has been rewritten. Is there a possibility for the code and contributions of the applicant to be evaluated?

I am changing the issue priority as per issue priorities → .

• The following points are just a start and don't necessarily encompass all the changes that may be necessary
• A specific point may just be an example and may apply in other places
• A review is about code that doesn't follow the coding standards, contains possible security issues, or does not correctly use the Drupal API; the single points are not ordered, not even by importance

imagelightbox.module

    $output .= '<p>' . (string) new TranslatableMarkup('<a href="@GIT"> git.drupalcode.org</a>', [
      '@GIT' => 'https://git.drupalcode.org/project/imagelightbox',
    ]) . '</p>';

The correct placeholder for URL starts with : (similarly to the placeholder used for another link). It must also be wrapped on double quotation marks, as reported on FormattableMarkup::placeholderFormat().

:variable: Return value is escaped with \Drupal\Component\Utility\Html::escape() and filtered for dangerous protocols using UrlHelper::stripDangerousProtocols(). Use this when using the "href" attribute, ensuring the attribute value is always wrapped in quotes

src/Plugin/Field/FieldFormatter/ImagelightboxFormatter.php

The \Drupal\image\Plugin\Field\FieldFormatter\ImageFormatter class is not part of the public API and cannot be used as parent class for classes implemented by a contributed module, differently from \Drupal\image\Plugin\Field\FieldFormatter\ImageFormatterBase which is a base class and therefore part of the public API.

I am changing priority as per Issue priorities → .

This thread has been idle, in the Needs work state with no activity for several months. Therefore, I am assuming that you are no longer pursuing this application, and I marked it as Closed (won't fix).

If this is incorrect, and you are still pursuing this application, then please feel free to re-open it and set the issue status to Needs work or Needs review, depending on the current status of your code.

Let's keep this application open for longer.