Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
21 Jul 2020 at 16:35 UTC
Updated:
15 Feb 2021 at 11:19 UTC
Jump to comment: Most recent
Comments
Comment #2
alexander.levitsky commentedComment #3
shaktikHi @alexander.levitsky,
Thanks for your contribution. Please fix coding standard issues.
Comment #4
alexander.levitsky commentedHi @shaktik
Thank you for your review, the listed issues were fixed.
Comment #5
harishh commentedHi alexander.levitsky,
Looks good. phpcs errors are fixed. Please apply the patch.
https://www.drupal.org/project/flexible_weather_api/issues/3161476
Comment #6
alexander.levitsky commentedHi @harishh
Thanks for your patch, it was applied.
Comment #7
alexander.levitsky commentedComment #8
alexander.levitsky commentedComment #9
mrweiner commentedChecklist
I don't think the README issue is a blocker but something to consider. Marking Needs Work mostly for the wide use of \Drupal calls and to see if you can sanitize YahooWeather::buildBaseString without breaking things.
Comment #10
mrweiner commentedActually, looking at things again, I think that the README.md probably does need to be updated. Check out https://www.drupal.org/node/2181737 for the README template.
Comment #11
avpadernoComment #12
alexander.levitsky commentedHello, @mrweiner!
Thank you very much for your detailed review. I have applied some recommendations to the dev branch.
1. The readme was updated.
2. The "\Drupal" calls were replaced at all places where it's possible. Only one place is left - it's a custom entity class Weather Service since I can't find a way how we can implement this and also found the documentation https://www.drupal.org/docs/drupal-apis/services-and-dependency-injectio...
where there is a note
3. Regarding sanitize YahooWeather::buildBaseString - I just used an example from the documentation for this service
https://developer.yahoo.com/weather/documentation.html#oauth-php
I'm not sure that I should adjust something here. Maybe you have more specific recommendations on what exactly I should do with this method?
Best Regards,
Alex.
Comment #13
ysamoylenko commentedThanks for your contribution!
Review:
* Project's code looks good for me.
* Have not found any issues during module installation and configuration.
* Unit tests are written.
I think that the module is ready to be covered by:
Drupal.org security advisory coverage
Comment #14
avpadernoComment #15
avpadernoThank 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 #16
alexander.levitsky commentedHi @kiamlaluno!
Thank you for updating my account and for the useful links! I will strive to continue to contribute to the community.
Best regards,
Alex.