This module is intended to be a tool for developers, analysts, and administrators that allows them to generate reports on a given Drupal installation.
It has been designed to enable the scalability of the module by adding new reports through plugins.
The project is now in an early stage of development with a limited number of reports focused on extracting information about existing content entities:
- Information about type of Content Entities and number of items.
- Información about the displays of the Content Entities: fields shown in each display, formatted applies and relationship with other entites.
We think that is a very useful tool to limit de risk in projects and give useful information during development process:
- To be able to identify the number of entities to be migrated.
- To detect entities that are not use and are may be deleted.
- It is useful to reduce de the complexity of profects
- To identify components in restyling projects
- Etc.
As company, we are installing this module in all our projects.
We are going to develop more interesting reports that allow us to have an xray picture of Drupal installations.
Project link
| Comment | File | Size | Author |
|---|---|---|---|
| nodes-languas-type.png | 27.96 KB | lpeidro | |
| displays-alpha.png | 221.73 KB | lpeidro | |
| content-entities-types.png | 63.76 KB | lpeidro | |
| list-actions-entities.png | 54.87 KB | lpeidro |
Comments
Comment #2
vishal.kadamThank you for applying! Reviewers will review the project files, describing what needs to be changed.
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.
To reviewers: Please read How to review security advisory coverage applications, What to cover in an application review, and Drupal.org security advisory coverage application workflow.
While this application is open, only the user who opened the application can make commits to the project used for the application.
Reviewers only describe what needs to be changed; they don't provide patches to fix what reported in a review.
Comment #3
vishal.kadam1. Remove below lines. It will be automatically added by the packaging script.
xray_audit.info.yml
2. It seems you have missed working on the coding standards. You can use the PHPCS tool for checking and resolving issues.
Comment #4
vishal.kadamComment #5
avpadernoFor 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 user who applies.
The purpose of these applications is reviewing a project to understand what the user who applies understands about writing secure code that follows the Drupal coding standards and correctly uses the Drupal API. A project without code committed by the user who applies cannot be used for these applications, especially when the user doesn't have the permission to commit code.
I see commits from Luis Ruiz.
Comment #6
lpeidro commentedHello vishal.kadam
Sorry for the missing work. I have already fix the problems with coding standards. Thank you very much for your review.
Hello apaderno, thank you for your comment, but these commit are done by me. The cause of the incongruity is the PC from I did the commit. Ones were done from my work PC and the another from my personal PC. The configuration of the user in the PC's are different but the Gitlab user is the same.
If you check my commits here https://git.drupalcode.org/users/Peidro/activity you wil see that are the same did by Luis Ruiz, Luis Peidro and lpeidro. In fact my complete name is "Luis Ruiz Peidro".
Comment #7
lpeidro commentedI changed the issue status to Needs review.
The commit that resolve the problems of coding standard is https://git.drupalcode.org/project/xray_audit/-/commit/e57111674e37ffff9...
Thanks.
Comment #8
vishal.kadamHello Luis,
I have reviewed the changes, and everything looks fine to me.
Let’s wait for other reviewers to take a look, and if everything goes fine, you will get the role.
Thanks
Comment #9
jitesh_1Hi @lpeidro,
This module works for me. I review this module and did not find any error.
Thanks.
Comment #10
avpadernosrc/Controller/XrayAuditGroupsController.php
Drupal 9 still requires PHP 7.3. A module that uses PHP 7.4 or PHP 8 features should explicitly require that PHP version, or require Drupal 10.x, which requires PHP 8.1 or higher versions.
src/Plugin/tasks/DisplaysGroup/XrayAuditEntityDisplaysPlugin.php
Both those comments contain wrong information: What described as entity type manager is not the entity type manager. The constructor is not for the
\Drupal\Component\Plugin\PluginBaseclass.src/Plugin/tasks/DisplaysGroup/XrayAuditEntityDisplaysPlugin.php
The code used for these applications is supposed to be complete. It should not contain methods that returns an empty string because the method has not been yet implemented.
Methods defined in an interface or parent class are documented with
{@inheritdoc}.Strings shown in the user interface need to be translatable.
src/Plugin/XrayAuditGroupPluginManager.php
The class name needs to include the full namespace.
Comment #11
lpeidro commentedHello apaderno:
Thank you very much for your excellent work. I will comment on your observations:
About the compatibility with PHP 7.3: I used "phpcompatibility/php-compatibility" to ensure that the modifications are in the commit: https://git.drupalcode.org/project/xray_audit/-/commit/77132e82ec7dbdcec...
About comments in code: I review the comments and I think that I fixed all the potential problems. I remove the empty methods and I am going to create an Issue in the module to develop those features:
Translatable strings: https://git.drupalcode.org/project/xray_audit/-/commit/ec5f71582d1dab0fc...
Comment #12
lpeidro commentedComment #13
lpeidro commentedComment #14
akshay.singh commentedComment #15
akshay.singh commented@lpeidro,
Reporter must not mark the status as RTBC. Only the reviewers is allowed to do so.
Thanks
Comment #16
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the Slack #contribute channel. So, come hang out and stay involved.
Thank you, also, 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 all the reviewers.
Comment #17
avpadernoComment #18
lpeidro commentedThank you very much for the work of all of you.