Closed jonathanbossenger closed 6 months ago
I am adding this here as it seems most appropriate:
A potential instruction as of how to incorporate wpcs into development workflow would possibly deserve a place here. The plugin review plugin is surely good but imo it’s better to just develop safely from the start, in the IDE, not go forth and back with scanners post-development. Also another tool that has saved my belated posterior a several times already is sonar cloud scanner. It’s free and has a few good things wpcs doesn’t look directly for.
Thanks @smileBeda this is the perfect spot to add it.
I was thinking that renaming this lesson from just being focused on the plugin security checker, and rather "Useful tools to detect security vulnerabilities" would be a good switch, and then we can include these tools.
Concerning the Sonar Cloud Scanner, I will need to check with the training team. We do have specific guidelines about suggesting paid services (I know there's a free trial, but ultimately it's a paid product, and I have to follow those guidelines.
Sonar Cloud is 100% free, forever (And easily integrated to VS Code, etc, for free too). It is only paid (10 USD per month) if you require scans on private repositories.
However, it is not a necessity to mention that service... if we can even just bring WPCS more to the dev attention it is already a huge gain.
Sonar Cloud is 100% free, forever
Thanks, can you point me to a link that shows that, I can't find that anywhere on the website.
Edit: Oh, wait, found it https://www.sonarsource.com/open-source-editions/.
https://github.com/WordPress/Learn/assets/180629/1144ded3-f0fe-44cd-a60d-e5f05ed69c27
Video ready for review
Please follow the Guidelines for reviewing content to review this lesson.
Great tutorial, @Jonathan! Provides a solid closure to this miniseries.
Please tick all items you've confirmed:
Great video @jonathanbossenger, Clear, concise, and easy to follow.
//publish
Details
Learning Objectives
Related Resources and Other Notes
Automation Code