- Issue created by @jaseerkinangattil
- 🇮🇳India vishal.kadam Mumbai
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 → .
- If you have not done it yet, you should run
- 🇮🇳India vishal.kadam Mumbai
1. Fix phpcs issues.
phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml social_auth_entra_id/ FILE: social_auth_entra_id/social_auth_entra_id.routing.yml ---------------------------------------------------------------------- FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES ---------------------------------------------------------------------- 15 | WARNING | Open page callback found, please add a comment before the line why there is no access restriction 24 | WARNING | Open page callback found, please add a comment before the line why there is no access restriction ---------------------------------------------------------------------- FILE: social_auth_entra_id/social_auth_entra_id.permissions.yml ---------------------------------------------------------------------- FOUND 1 ERROR AFFECTING 1 LINE ---------------------------------------------------------------------- 3 | ERROR | [x] Expected 1 newline at end of file; 2 found ---------------------------------------------------------------------- PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY ---------------------------------------------------------------------- FILE: social_auth_entra_id/src/Plugin/Block/EntraIdLoginBlockBlock.php ---------------------------------------------------------------------- FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES ---------------------------------------------------------------------- 29 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead 44 | WARNING | Unused variable $link. 52 | WARNING | Unused variable $link. ---------------------------------------------------------------------- FILE: social_auth_entra_id/tests/src/Unit/Controller/SocialAuthEntraIdControllerTest.php ---------------------------------------------------------------------- FOUND 6 ERRORS AFFECTING 6 LINES ---------------------------------------------------------------------- 33 | ERROR | Missing @var tag in member variable comment 35 | ERROR | Missing member variable doc comment 36 | ERROR | Missing member variable doc comment 37 | ERROR | Missing member variable doc comment 38 | ERROR | Missing member variable doc comment 123 | ERROR | The array declaration extends to column 81 (the limit is 80). The array content should be split up over multiple lines ----------------------------------------------------------------------
2. FILE: README.txt
Replace README.txt with README.md, that should follow the content and formatting described in README.md template → .
3. FILE: social_auth_entra_id.module
/** * @file * Primary module hooks for social_auth_entra_id module. */
Drupal does not have primary and secondary hooks. Instead of that, it is preferable to use the usual description: Hook implementations for the [module name] module. where [module name] is the name of the module given in its .info.yml file.
- 🇮🇳India jaseerkinangattil Bangalore
All the coding standards issues are fixed in the new release
- 🇮🇳India vishal.kadam Mumbai
Rest seems fine to me.
Let’s wait for other reviewers and Code Review Administrator to take a look and if everything goes fine, you will get the role.