Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 Apr 2016 at 04:59 UTC
Updated:
27 Jan 2017 at 17:26 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
PA robot commentedGit clone command for the sandbox is missing in the issue summary, please add it.
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
dkolarevic commentedHi surendra77c,
Please check http://pareview.sh/pareview/httpgitdrupalorgsandboxsurendra77c2703111git and try to fix errors.
Manual review:
Lines 44 and 53 - you declared $settings variable but never used it.
Lines 114-115 - you can combine those nested ifs in one if statement.
Comment #4
surendra77c commentedRequested changes compleated .
Comment #5
surendra77c commentedHi Team can I get the update on the module when it will be tested .
Comment #6
mike.davis commentedHi @surendra77c, could you please update the issue with the URL of your sandbox module, as this will make it easier to review.
Comment #7
mike.davis commentedHaving had a look at the Pareview report there is still a lot of code standard errors which will need to be fixed.
I have managed to find your sandbox module, and having had a look through the code, there is a
print_rin the hook_node_presave function.Please remove this as this function doesn't look like it is needed and there shouldn't be a print_r in any production code.
Comment #8
mike.davis commentedUpdated the status
Comment #9
mike.davis commentedComment #10
surendra77c commentedHi Team ,
Requested changes completed can you please review the code .
Comment #11
surendra77c commentedHi Team ,
Can you please review the code .
Comment #12
mike.davis commentedHi @surendra77c,
Although you have removed the print_r, the coding standards raised in the Pareview report are still present.
You should look at fixing these first so that this report passes before continuing.
Thanks
Mike
Comment #13
immanuel.paul commentedHi surendra77c,
I have created a patch for your module based on pareview.sh report. Please review the patch and apply to your code. Good luck :)
Thanks
Immanuel Paul
Comment #14
surendra77c commentedHi Team ,
Thanks @ Immanuel Paul for your patch , that has help me to fix my module issue . I have update the code can you please review the code .
Comment #15
surendra77c commentedHi Team ,
Can you please review the code .
Comment #16
surendra77c commentedHi Team ,
Can you please review the code .
Comment #17
gisleTo get people to review your application, you need to set its state to "Needs review", not "Active". Please see project applicaton workflow.
If you're impatient, to give your application a higher priority, please join the review bonus system. If you participate in the system by doing manual reviews, you can put yourself on the high priority list. Applications with
PAReview: bonustag are more likely to receive attention from reviewers and git administrators.Comment #18
ashwinshAdded Project link and Git URL for this poject.
Comment #19
surendra77c commentedHi gisle ,
I have set the project to review state , can you please review the code now .
Comment #20
surendra77c commented.
Comment #21
gisleYour code isn't clean enough yet for me to bother with doing a code review. While you're waiting for one, you can work on the following:
Fix the coding style errors pointed out by http://pareview.sh/pareview/httpgitdrupalorgsandboxsurendra77c2703111git (style errors don't block promotion, but it is more difficult and more work to manually review code with style errors, so I usually don't do a manually review until the code is clean).
Remove the patch that is included in your your repo, it doesn't belong there.
Your project page is empty. What is the use case for this module? As far as I am able to tell, it creates a text field to hold an author name. That field that can be added to the content type under "manage fields". Adding a text field to a content type is already in core. What utility does your module provide that is not already in the core fields module? Please take a moment to make your project page follow the Project page template and it may be a good idea to also read tips for a great project page.
Set the correct values for maintenance status and development status.
Make your README.txt follow the guidelines for in-project documentation and the README.txt Template.
PS: Please also note that there are more applications that yours that Needs review. Some have been waiting longer than yours.
Comment #22
chaitanya17 commentedHi @surendra77c,
I have reviewed your module, nice to see author field to content type created.
You have written
hook_schema($field) { //logic }in cck_author.module file.Proper way will be using .install file. please move related code to install file.
Thanks.
Comment #23
chaitanya17 commentedComment #24
pookmish commentedManual Review
Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
Comment #25
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #26
surendra77c commentedHi ,
I have moved schema code to .install file please review the code .
Comment #27
surendra77c commentedTeam please review the code .
Comment #28
surendra77c commentedComment #29
satyam upadhyay commentedHi surendra77c,
I reviewed your module, but it's not clear what you want to implement using this module in cck fields and nothing to be add from the patch that is added in the clone folder.
And you can see nothing happened using this module http://www.screencast.com/t/HKXRD1uYVb6
I think that you want to implement, this can be achieve by using core cck_field by added a text field in to any ctype
Regards
Satyam
Comment #30
satyam upadhyay commentedComment #31
satyam upadhyay commentedComment #32
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.