This module provides a basic integration with the PriceSpider service. Currently this module only provides support for the page-embedded generic Where-to-Buy (WTB) experience.
I did not realize there was another module available before taking maintainership of this one. I just discovered this and have opened an issue to start a dialog about collaborating, see https://www.drupal.org/project/price_spider/issues/3104504.
This module differs from https://git.drupalcode.org/project/price_spider b/c it
- Works well with multilingual sites via active language where as price_spider works with a single configured language
- Has clear configuration steps in README vs price_spider
Project link
https://www.drupal.org/project/pricespider
Git instructions
git clone --branch 8.x-1.x git@git.drupal.org:project/pricespider.git
PAReview checklist
https://pareview.sh/pareview/https-git.drupal.org-project-pricespider
Comments
Comment #2
rksyraviYou'll need to resolve all the errors and warnings of the file CHANGELOG.md, pricespider.module, pricespider.info.yml files.
CHANGELOG.md: reduce the characters per line exceeding 80, if exceeded start with the new line to continue.
Comment #3
rksyraviAlso ensure not to use deprecated code in your modules Eg: drupal_set_message() you have used in .module files.
Comment #4
Ankush_03Comment #5
jasonawantThanks for the review.
I've removed drupal_set_message usages, see #3079967: deprecated drupal_set_message() method used.
Regarding the other items identified in https://pareview.sh/pareview/https-git.drupal.org-project-pricespider, see below.
These items are found in markdown file, there is ongoing discussion about markdown coding standards, see #2952616: Adopt CommonMark spec for Markdown files. I think the offending lines include links, which shouldn't be flagged, see #2860121: Warning on line length with markdown. If I count characters of the rendered markdown, some do exceed 80 characters. However, the reported line count by pareview will still flag these given it is reporting all characters, e.g. 202 characters...not the 81 rendered markdown characters.
Any recommendations about this?
I think the following are false positives
In the 2nd comment above, there's mention of an issue with the pricespider.info.yml; what's the issue there?
Comment #6
rksyraviAs you can see form the
in
pricespider.module
file, you are using function mentioned below:you have used
$sku_field
variable to compare with, but this variable is not defined, you'll need to defined.Eg:you can define as
array or string or int
.Comment #7
apadernoActually, that code is comparing a variable that has not been initialized with the output of a method (in the first line). Maybe that comparison should be an assignment.
Comment #8
rksyraviYeah totally agree with @kiamlaluno, that variable should be an assignment, if not then it's better to define before using further.
Comment #9
vuilThank you for the contribution!
I updated the project's summary. And I set the issue status to Needs work.
Please also fix the following issues:
1. The
$sku_field
variable is undefined in the 'pricespider.module' file.2. Please update your 'CHANGELOG.md' file to have no more than 80 characters per line.
Comment #10
vuilComment #11
jasonawantIndeed! I incorrectly saw these as false positives. I've updated as a variable assignment like other usages of this pattern.
See https://pareview.sh/pareview/https-git.drupal.org-project-pricespider
Hi @vuil! Did you comment #5, any recommendations about how to move that forward?
Comment #12
vuilOh, thank you. Good work!
I found an issue through the manual code review:
- Please, \Drupal calls should be avoided in classes, use dependency injection instead (in
src/Routing/PriceSpiderRoutes.php
).Comment #13
jasonawantAlright, this is fixed. See https://git.drupalcode.org/project/pricespider/commit/3e8ac9f43733f5c760...
Comment #14
jasonawantalright, changelog updated! https://www.drupal.org/project/pricespider/issues/3104738
Comment #15
Ankush_03Code Looks Good to me Going to RTBC !
Comment #16
jasonawantGreat, thank you everyone for reviewing and all the feedback! What's the next step?
Comment #17
apadernoThank 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 IRC #drupal-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 dedicated reviewers as well.
Comment #18
jasonawantAwesome! Thank you everyone for reviewing!
Comment #19
Ankush_03Thank you @jasonawant for contribution.
Comment #20
rksyraviHi @jasonawant,
You're welcome.