Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
24 Jun 2019 at 18:50 UTC
Updated:
18 Aug 2019 at 08:44 UTC
Jump to comment: Most recent
Comments
Comment #2
Mirroar commentedI forgot to mention that I ran the project through PAReview and fixed the few issues that came up.
Thanks to anybody that takes the time to review.
Comment #3
bekirdag commentedHello,
You may like to create automated tests and have an alpha branch instead of a stable release since a views injection module is a big deal and there are open issues for the module currently.
One more thing, you have to add a dependency on your info yml file for "views" since your module depends on it.
Other than those, it looks good to me,
Thanks for sharing!
Comment #4
Mirroar commentedThank you for the feedback.
You must have looked at the 1.0 release, because the dev version has the dependency to views added.
I completely agree that there should be tests added, I'll try to add them in the near future.
I'll get back to you once the following issues are fixed, which should be good enough for a new beta or RC release:
#3063769: Overflow of injected items leads to strange result counts
#3063868: Add tests
Comment #5
avpadernoThank you for applying! I added the PAReview checklist link. Reviewers will check the project and post comments to list what should be changed.
Comment #6
vuilHello,
Thank you for the contribution!
Please always keep attention on your project (module) issues, always work on and update them regular. You are the maintainer.
https://www.drupal.org/project/issues/views_inject?categories=All
Comment #7
avpadernoComment #8
vuilGood work!
There is not any security issue into the code.
Nice tests also!
* Just keep in mind to use for tests only PHP version equal or greater than PHP7.
Comment #9
Mirroar commentedThanks everybody for your valuable feedback! The addition of tests especially helped the project's stability, which is great because I was meaning to learn more about testing in Drupal anyway.
I just fixed the last of the mentioned issues and pushed a tag for a release candidate so people can start using that.
Comment #10
vuilComment #11
vuilComment #12
Mirroar commentedI don't want to sound impatient, but I'd like to know if there is anything I can do to move this along? I'd love to release 8.x-1.1 (Ideally with security coverage) so 8.x-1.0 no longer shows up as "Recommended by the project’s maintainer".
Comment #13
avpadernoThe status was already changed to Reviewed & tested by the community, but then reverted to Needs review. I take there was a reason to review the application, but that should be asked to the user who changed back the status.
Comment #14
vuilThank you for the contribution!
I was need more time to check everything in details, and yes, now the code is OK.
The status is updated.
Comment #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.