The Ultimate WordPress Plugin Main File about small-project HOT 8 CLOSED

Thank you for all four of your bullet points!

• backslashes will be gone with use function ...;
• WPCS is an anti-review laser gun :) no wonder PSR-12 exists, WPCS is for beginners and visually impaired people 👉 quote from https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#declaring-arrays
• filtering the results gives the user an unhealthy dose if liberty, making it pass with requirements unmet equals not checking anything at all - I know the whole WordPress ecosystem is about unhealthy dose if liberty, I think I cannot join...

I come from a decent embedded world where you flip one bit and the whole device goes to the bin 🗑️

from small-project.

1. list of parts
2. order/dependency
3. structure, modularity
4. testability
5. namespace Company\WordPress\PluginName;

from small-project.

Hello @cliffordp! https://twitter.com/TourKick/status/1339807246058975234
This is a theoretical research on main plugin file parts: The Ultimate Main Plugin File.
Would you like to contribute?

from small-project.

Hi, @szepeviktor - I've not seen this repo before and am unsure what you're asking of me - but I don't know if I've ever needed a boilerplate for something temporary, and I'm curious about the use cases you've come across and how this might relate to WordPress.

from small-project.

the use cases you've come across and how this might relate to WordPress.

I just need a solid documentation and implementation examples of main WordPress plugin part (listed above).
It would be nice to link to it when I find a sub-optimal plugin...

from small-project.

OK, thanks for sharing. Feel free to reference https://github.com/cliffordp/cliff-wp-plugin-boilerplate as would be helpful to you.

from small-project.

Done! 😄

@cliffordp Could you take a look at the new main file and classes in src?
I would be thankful for a code review.

from small-project.

Hi. I skimmed through. Here are some notes:

1. It's recommended to not use a closure (anon function) with hooks (action/filter) because then they cannot easily (if at all) be un-hooked
2. Personally, I find the global namespace \ to clutter the code viewing but that's likely just what I'm used to - so no changes if you feel it important.
3. Code styling from WordPress, should you choose to adopt it (other than array(), which I prefer as its short form), would say to have more spacing, e.g. \add_action('admin_notices', ..., 0, 0); would be \add_action( 'admin_notices', ..., 0, 0 );
4. One big use of the Requirements class in an if is of course fine for running the code, but personally I'd want to see the Requirements class' result filterable via apply_filters(), passing the args used as one of the parameters. Just an idea.

Good luck going forward however you see fit. Keep up the good work :)

from small-project.