- Issue created by @enriquelacoma
- 🇮🇳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
- Status changed to Needs work
16 days ago 5:06am 10 June 2024 - 🇮🇳India vishal.kadam Mumbai
1. FILE: pwbi.module
/** * Implements hook_form_FORM_ID_alter(). * * Add tenant field to Power Bi service principal auth workflow configuration. */ function pwbi_form_oauth2_client_edit_form_alter(&$form, FormStateInterface $form_state, $form_id) {
The description for that hook should also say for which form that hook is implemented, either by indicating that with the name of the class that implements the form (namespace included) or the form ID (which is usually indicated by
getFormId()
).2. FILE: src/PowerBiEmbed.php
/** * Constructor for PowerBiEmbed. * * @param \Drupal\Core\State\StateInterface $state * The state service. * @param \Drupal\Core\Logger\LoggerChannelFactoryInterface $loggerFactory * The logger service. * @param \Drupal\pwbi\Api\PowerBiClient $pwbiClient * The PowerBi RestAPI client. */ public function __construct(
FILE: src/Api/PowerBiClient.php
/** * Constructor for PowerBiClient. * * @param \Drupal\Core\State\StateInterface $state * The state service. * @param \Drupal\Core\Logger\LoggerChannelFactoryInterface $loggerFactory * The logger service. * @param \GuzzleHttp\ClientInterface $httpClient * The http_request service. * @param \Drupal\oauth2_client\Service\Oauth2ClientService $auth * The PowerBi authentication service. * @param \Drupal\Core\File\FileUrlGenerator $fileUrlGenerator * The file url generator service. * @param \Drupal\Core\File\FileSystemInterface $fileSystem * The file system service. */ public function __construct(
FILE: src/Form/PowerBiEmbedConfigForm.php
/** * Constructor for PowerBiEmbedConfigForm. * * @param \Drupal\pwbi\PowerBiEmbed $pwbiEmbed * The PowerBi embed service. */ public function __construct(
FILE: src/Form/PowerBiRestApiTestForm.php
/** * Constructor for PowerBiRestApiTestForm. * * @param \Drupal\pwbi\Api\PowerBiClient $client * The PowerBi api client service. */ public function __construct(PowerBiClient $client) {
FILE: src/Plugin/Field/FieldFormatter/PowerBiEmbedFormatter.php
/** * {@inheritDoc} */ public function __construct(
FILE: src/Plugin/Field/FieldWidget/PowerBiEmbedWidget.php
/** * {@inheritdoc} */ public function __construct(
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.
- 🇪🇸Spain enriquelacoma Zaragoza
@vishal.kadam thanks for the review.
I changed the documentation for the hooks and the __construct methods.
Just in case, I also applied some changes from the eslint pipeline.Regards
- Status changed to Needs review
15 days ago 9:08am 11 June 2024 - 🇮🇹Italy apaderno Brescia, 🇮🇹
Thank you for your contribution!
I updated your account so you can now opt into security advisory coverage for any project you created and every project you will create.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 → !
Thank you for your patience with the review process. 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 also the dedicated reviewers as well.
- Assigned to apaderno
- Status changed to Fixed
15 days ago 9:24am 11 June 2024 Automatically closed - issue fixed for 2 weeks with no activity.