Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Sep 2011 at 16:18 UTC
Updated:
12 Jan 2013 at 12:44 UTC
Jump to comment: Most recent file
Comments
Comment #1
sreynen commentedHi mouize,
I did an initial review an opened a couple issues in the project issue queue. Please move this back to "needs review" when those are fixed.
Comment #2
mouize commentedI've corrected all issues.
Thanks for your help.
Comment #3
klausiComment #4
misc commented@mouize has been contacted to ask if the application is abandoned.
http://drupal.org/node/894256
Comment #5
misc commented@mouize replied that the application is not abandoned.
Comment #6
mouize commentedBack again,
Okey, I made a lot of changes.
I cleaned the code and comments with code review.
I hope that this one is the good one.
Thx.
Comment #7
darrell_ulm commentedHello, first off used the online auto scanner. Found many coding style issues. These are included in the attached file. Feel free to run the scanner yourself to resolve these issues.
For Drupal coding conventions please refer to:
http://drupal.org/coding-standards#comment
http://drupal.org/node/1354
Also you need to setup master to just have README. Backing up everything is wise before you do this of course. See:
http://drupal.org/node/1127732
So some more explainations:
With functions like:
bh_project_type_load($type) {./inc/behat_integration_requests.inc: all functions should be prefixed with your module/theme name to avoid name clashes. See http://drupal.org/node/318#naming [1]
Instead of using "bh" use "behat" which is your module name, and elsewhere on the other functions.
Your .module file needs a @file comment header, check elsewhere also. The above coding standard links will show you the way.
File header on behat.css would be nice as well as the tpl.php files for readability.
That will give you some things to work on for a while. Good luck.
Comment #8
patrickd commenteddo NOT wrap text in hook_menu functions with t()!
he already moved into a version specific branch..
@darrellulm
what you're doing here is really not very helpfull,
feel free to review applications but please give a little more effort
Comment #9
darrell_ulm commented@patrickd
Right, again I didn't know MASTER branch was allowed to have HEAD distro in it before release. It appears that changed again as before MASTER was supposed be empty. Thanks for the update of the change!Comment #10
mouize commentedHi,
I've just cleaned the code, there are some other minor issue with ventral, but i don't understand the point.
The major problems have been corrected.
Thx.
Comment #11
jpontani commentedReview
/behat_field/behat_field.module
The following function's logic is confusing. You're using three negations where you could use none. Your function returns "not empty" (FALSE) if either the label or value are not empty. Otherwise, if BOTH label and value are empty, your field is "empty" (TRUE).
Could be rewritten as (see the logic from my statement above):
Will add some other manual review stuff later, don't want this post to be too long.
Comment #12
mouize commentedCorrected for the last one.
Comment #13
luxpaparazzi commentedThis automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.
Manual review:
1. it would be best prefixing all functions, global variables etc with your project shortname:
2. Non initalized variable:
... the same in:
_behat_integration_command()
3. Why do you use redundant functions:
4. allready => already (see behat_integration_project_form_validate)
5. CSS:
should be:
Comment #14
luxpaparazzi commentedTyp:
You need 3 reviews for adding the review bonus tag (check the link above).
If you had time, you could take a look at http://drupal.org/node/1302786
Comment #15
mouize commentedSo,
For those one, i'll stay with substr, the drupal_ equivalent is not necessary.
Comment #16
jthorson commentedCan you address the elements flagged during the manual review in comment #13? (I wasn't sure if you missed the prefixed variable names comment, or had a valid reason for not doing so ... if the latter, then please provide an explanation as to why.)
Apologies if you have addressed them already ... admittedly, I didn't look past the first one.
Comment #17
mouize commentedYeah, the first one wasn't prefixed, my mistake.
Others are prefixed by bi_ (behat_integration initial).
Comment #18
rico.schaefer commentedPlease check the coding standard again. You can see the problems at http://ventral.org/pareview/httpgitdrupalorgsandboxmouize1272110git
Comment #19
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.