Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2020 at 08:21 UTC
Updated:
20 Jun 2021 at 13:39 UTC
Jump to comment: Most recent
Comments
Comment #2
avpadernoComment #3
shaktikHi @Miguelpamferreira.
Fix the Drupal coding standards.
Comment #4
miguelpamferreira commentedHello, I have applied the changes to the code on everything but the concatenation of t() functions warnings as I don't see any sensible way to make that work.
Comment #5
batkorCorrect dev branch.
i right changed dev branch?
Comment #6
batkorPlease reread code standard
https://git.drupalcode.org/project/extlog/-/blob/8.x-1.x/extlog.module#L54
Your testing your module for d9?
please remove and change deprecate code https://git.drupalcode.org/project/extlog/-/blob/8.x-1.x/extlog.module#L200
Comment #7
miguelpamferreira commentedThank you batkor
The deprecated code in extlog.module#L200 is now fixed
Could you please be a bit more specific about what is wrong with extlog.module#L54?
I don't see anything wrong with that line
Comment #8
avpadernoThere are spaces at the end of some lines, in this code. (I added a comment at the end to show which lines have trailing spaces.)
There are other lines with trailing spaces.
There should not be trailing spaces, but I would consider that not so relevant to block an application.
Comment #9
tr commentedWhile there are still coding standards problems which should be fixed, there are bigger things that are wrong with this project.
Specifically, 8.x-1.1 and 8.x-1.2 and @branch are not valid branch names. Your code needs to be in the 8.x-1.x branch. Development releases like 8.x-1.x-dev will be made with the HEAD of the 8.x-1.x branch. Testing will be done against the 8.x-1.x branch. And when you are ready to make fixed-point releases, you should add a TAG for the release to the 8.x-1.x branch. So 8.x-1.5 will be a TAG on the 8.x-1.x branch, etc.
Even more confusing, you also have 8.x-1.1 and 8.x-1.2 tags on your 8.x-1.2 branch and you also have a 8.x-1.1 tag on your 8.x-1.1 branch and you also have 8.x-1.1 and 8.x-1.2 and 8.x-1.4 tags on your 8.x-1.x branch. And I'm not sure exactly what branch the 8.x-1.3 tag is attached to ... You're going to have to know a lot about git to figure out how to fix this mess. It's a real problem because if I say
git checkout 8.x.1.2, what code does that give you? Git will use the tag first, rather than the branch, so if you're on the 8.x-1.1 branch it will checkout the 8.x-1.2 tag on the 8.x-1.1 branch, NOT the 8.x-1.2 branch. Likewise, there is no way of telling which branch was used to make the 8.x-1.2 release, etc.The 8.x-1.1 and 8.x-1.2 "branches" should be deleted, but before you do that you have to make sure that the latest and best code is moved to the 8.x-1.x branch. For example, the ExternalLogger class (which I believe is the most important part of this module!) is WRONG in 8.x-1.x. It is a Unit test case in the wrong directory with the wrong namespace for that directory. And there is no ExternalLogger class implementing LoggerInterface in 8.x-1.x ! This doesn't seem to be a problem in the 8.x-1.2 "branch", just in the 8.x-1.x branch. This is also why your automated tests are failing for the 8.x-1.x branch.
Part of the confusion above with coding standards is that perhaps you are fixing them in some place other than the 8.x-1.x branch? The best thing to do is to make sure you put everything into 8.x-1.x then delete the two faulty branches. We will be glad to help you in this thread if you run into any problems - if you've made releases from one of the branches with a wrong name then you might need a drupal.org administrator to help you correct that.
Comment #10
miguelpamferreira commentedThe module has been reviewed and the branches pruned.
If you would be so kind as to review once more.
Thank you
Comment #11
klausiThe Git commits are not connected to your user account. You need to specify an email address. See https://www.drupal.org/node/1022156 and https://www.drupal.org/node/1051722
manual review:
Otherwise looks good to me!
I think we have enough code here to do a normal full project promotion.
Thanks for your contribution, Miguel!
I updated your account so you can opt into security advisory coverage now.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on Slack or IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, 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.
Thanks to the dedicated reviewer(s) as well.