[1.0.x] Session Reminder

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

1. Fix phpcs issues.

phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml session_reminder/

FILE: session_reminder/session_reminder.info.yml
--------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
--------------------------------------------------------------------------------
 8 | WARNING | All dependencies must be prefixed with the project name, for example "drupal:"
--------------------------------------------------------------------------------

FILE: session_reminder/src/Form/ConfigForm.php
--------------------------------------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
--------------------------------------------------------------------------------
 33 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead
 34 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead
 77 | WARNING | Role::loadMultiple calls should be avoided in classes, use dependency injection instead
--------------------------------------------------------------------------------

FILE: session_reminder/src/Form/ModalForm.php
--------------------------------------------------------------------------------
FOUND 3 ERRORS AND 2 WARNINGS AFFECTING 5 LINES
--------------------------------------------------------------------------------
  31 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead
  97 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead
 101 | ERROR   | The $_COOKIE super global must not be accessed directly; inject the request_stack service and use
     |         | $stack->getCurrentRequest()->cookies->get($sessionCookieName) instead
 102 | ERROR   | The $_COOKIE super global must not be accessed directly; inject the request_stack service and use
     |         | $stack->getCurrentRequest()->cookies->get($sessionCookieName) instead
 103 | ERROR   | The $_COOKIE super global must not be accessed directly; inject the request_stack service and use
     |         | $stack->getCurrentRequest()->cookies->get($sessionCookieName) instead
--------------------------------------------------------------------------------

2. FILE: session_reminder.module

/**
 * @file
 * Describes hooks.
 */

The usual description for a .module file is Hook implementations for the [module name] module. where [module name] is the module name given in the .info.yml file.

Hi and thank you!
I've fixed it in 1.0.x branch and updated issue status to "Need Review".

Thanks

Rest looks fine to me.

Let’s wait for a Code Review Administrator to take a look and if everything goes fine, you will get the role.

I am changing priority as per Issue Priorities → .

Hi, there are some news about this module?
Tnx

Thank you for your contribution and for your patience with the review process!

I am going to update your account so you can opt into security advisory coverage any project you create, including the projects you already created.

These are some recommended readings to help you with maintainership:

• Dries → ' post on Responsible maintainers
• Maintainership →
• Git version control system →
• Issue procedures and etiquette →
• Maintaining and responding to issues for a project →
• Release naming conventions → .

You can find more contributors chatting on Slack → or IRC → in #drupal-contribute. So, come hang out and stay involved → !
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review → . I encourage you to learn more about that process and join the group of reviewers.

I thank the dedicated reviewers as well.

Automatically closed - issue fixed for 2 weeks with no activity.