evonox

Thank you @lumiblog for your answer.

So, if I understand it right, the primary goal of WPCS is to guarantee that one plugin does not conflict with others.

The strong encapsulation of all the plugin application code is the primary goal of the framework I am creating. You will specify the namespace prefix for the all the plugin application code and the plugin prefix in one place. The framework will use this prefix everywhere in the WordPress Core APIs automatically without the need for the plugin author even to care. All of that using DI container with OOP programming.

The main plugin file will look like this.

<?php

/*
 * Plugin Name:       WordPress Plugin Framework Demo
 * Plugin URI:        https://github.com/evonox/wordpress-plugin-framework.git
 * Description:       WordPress Plugin Framework Demo
 * Version:           1.0.0
 * Author:            Viktor Prehnal
 * Author URI:        https://www.viktorprehnal.cz/
 * License:           MIT
 * License URI:       https://opensource.org/license/mit
 */

if (! defined("ABSPATH")) {
    exit;
}

const __PLUGIN___MAIN_FILE_PATH = __FILE__;

require_once __DIR__ . "/vendor/autoload.php";
require_once __DIR__ . "/Framework/bootstrap.php";

Basically the framework will work with WordPress in the Inversion of Control fashion. The plugin application code will communicate with most WP Core APIs through the framework.

I would need a help to figure out then deeper, what might be allowed for compliance and what not.

Would it be possible to request someone from WP Core Team as supervisor of what is allowed and what not? The framework will be FOSS available upon possibly Apache 2.0 license.

• This reply was modified 2 months, 3 weeks ago by evonox.