This module allows users to expose fields to visitors. It adds another filter with the Exposed fields filter in filter criteria.
User can add a keyword and select a field to search that keyword in. If the field dropdown is not selected it will search the keyword in all the fields which are exposed to visitors.
Project Page: https://www.drupal.org/sandbox/shabirahmad/2642802
Clone Command: git clone --branch 7.x-1.x http://git.drupal.org/sandbox/shabirahmad/2642802.git views_exposed_field_filter
Review bonus:
https://www.drupal.org/node/2643522#comment-10725918
https://www.drupal.org/node/2642690#comment-10726022
https://www.drupal.org/node/2645832#comment-10726070
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | pareview.txt | 3.26 KB | pushpinderchauhan |
Comments
Comment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxshabirahmad2642802git
Fixed the git clone URL in the issue summary for non-maintainer users.
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
atul4drupal commentedHello shabirahmad,
To make your module more standard please add README.txt file to your module.
Its good practice to add one and brief others about the module in it.
Comment #4
atul4drupal commentedHello shabirahmad,
In addition to the above point, just test your module for common code formating errors at "http://pareview.sh".
For instance :
1) In module file add ablank line at end of the file.
2) Function comment ends with a period.
You can see the automated error report at 'http://pareview.sh/pareview/httpgitdrupalorgsandboxshabirahmad2642802git'.
Comment #5
shabirahmad commentedComment #6
shabirahmad commentedComment #7
shabirahmad commentedThank you Atul. I have made some changes based on automated review. However, I can't change methods name. For instance the automated review tells me to change option_definitions() to OptionsDefinition() but I can't change that as I am overriding parent function here.
Comment #8
jibranNW for the following errors which are not yet addressed.
Comment #9
shabirahmad commentedThanks, Jibran! I will start working on it.
Comment #10
shabirahmad commentedAll errors pointed by JIbran are fixed now. We have now only naming convention issues which we can't fix as we are overriding base class functions.
Comment #11
shabirahmad commentedAnyone Please rtbc it!
Comment #12
fishfree commentedIf there is a config option which can hide dependent exposed filters, this module will be much more valuable.
Comment #13
shabirahmad commented@fishfree. Thanks but this could be achieved in next releases. For now I would like to have people find bugs and release blockers
Comment #14
shafqat1982 commentedI have reviewed it, It looks like working as expected no release blockers.
Comment #15
dawehnerJust quickly scanned through the module. It looks solid in general, especially given how similar it is compared to the combine filter.
Comment #16
shabirahmad commentedComment #17
web4pro_co commentedHello,
1. Please check coding standard http://pareview.sh/pareview/httpgitdrupalorgsandboxshabirahmad2642802git
2. Please add more information to README about how use your module.
Thanks for your work!
Comment #18
shabirahmad commented@web4pro_co: thanks for your time to review the module.
Automatic review shows only naming conventions which has already been discussed #10. Since we are overriding existing views functions so it would have suppose to be the same.
I will update the readme file though!
Thanks!
Comment #19
heykarthikwithuLooks fine, needs an updated readme :)
Comment #20
shabirahmad commentedThanks, @heykarthikwithu I have updated readme file. It has detailed instruction.
Comment #21
sandipauti commentedHello,
1. Add more step to install and use your module, please refer below template to write README file.
https://www.drupal.org/node/2181737
2. Add new line to each file according to Drupal coding standard.
https://www.drupal.org/coding-standards
Thanks for your hard work, Over all great work.
Comment #22
shabirahmad commentedthanks @sandi. I have made those changes!
Comment #23
pushpinderchauhan commentedAutomated Review
Best practice issues identified by pareview.sh / drupalcs / coder. Yes, however those seems to be false to me but you should take a look on attached file (pareview.txt) once.
FYI...Review of the 7.x-1.x branch (commit 3f60fa1):
Manual Review
I am not seeing any blocking issues, code is very well organised so I am keeping RTBC. Assigning to @mpdonadio for a second look if he has time.
Comment #24
shabirahmad commentedThanks! The pareview.txt naming standard can't be followed since we are overriding existing views classes. It's been discussed above.
Comment #25
mpdonadioAutomated Review
Review of the 7.x-1.x branch (commit 3f60fa1):
Not attaching output, as they all look like false reports b/c Views requirements.
Manual Review
README is really lean. You should expand it.
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
Not seeing anything to block this, especially since @dawehner gave this a once over from a Views perspective.
If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
Comment #26
mpdonadioThanks for your contribution, shabirahmad!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on 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.