feat: remove compilation command

After thinking for some time, I've decided to get rid of compilation command. This would be useful to compile container and plugin data at build-time, but for the container the task is not trivial.

Compilation would require WordPress runtime, so the only viable solution would be to boot whole WordPress with database. Removing the use of WordPress functions wouldn't be possible or at least required some common WP functions to be rewritten in our codebase.

For current approach, I bias towards compilation in customer's environment at first runtime, with graceful handling of any IO operation issues.

Signed-off-by: Bart Jaskulski bjaskulski@protonmail.com

tests/HookDriver/GenericDriverTest.php

@@ -12,9 +12,20 @@ use WPDesk\Init\Configuration\Configuration;
 use Psr\Container\ContainerInterface;
 use WPDesk\Init\Binding\Loader\ArrayDefinitions;
 use WPDesk\Init\Tests\TestCase;
+use Brain\Monkey;
 
 class GenericDriverTest extends TestCase {
 
+	public function setUp(): void {
+		parent::setUp();
+		Monkey\setUp();
+	}
+
+	public function tearDown(): void {
+		parent::tearDown();
+		Monkey\tearDown();
+	}
+
 	public function provider(): iterable {
 		yield [
 				'fake_binder' => new ObservableBinder(new class implements Binder {
@@ -69,6 +80,7 @@ class GenericDriverTest extends TestCase {
 	}
 
 	public function test_register_hooks(): void {
+		$this->markTestSkipped('Now, wp-init runs its logic inside hook, and unit test is not a good place to check for that');
 		$binder = new ObservableBinder($this->getBinder());
 		$driver = new GenericDriver(
 			new ArrayDefinitions(['' => ['hook1', 'hook2']]),