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

src/Kernel.php

@@ -92,10 +92,10 @@ final class Kernel {
 		return preg_replace( '/[^\w_]/', '_', implode("_", [ $plugin->get_slug(), $plugin->get_version(), 'container' ]) );
 	}
 
-	private function initialize_container( Plugin $plugin, bool $useCache = true ): Container {
+	private function initialize_container( Plugin $plugin, bool $use_cache = true ): Container {
 		$original_builder = new DiBuilder();
 
-		if ( $this->is_prod() && $useCache ) {
+		if ( $this->is_prod() && $use_cache ) {
 			$original_builder->enableCompilation(
 				$this->get_cache_path(),
 				$this->get_container_name( $plugin )
@@ -114,7 +114,12 @@ final class Kernel {
 
 		try {
 			return $builder->build();
-		} catch ( \Exception $e ) {
+		} catch ( \InvalidArgumentException $e ) {
+			if ( $use_cache === false ) {
+				// It means, that saving to disk was not an issue.
+				throw $e;
+			}
+
 			return $this->initialize_container( $plugin, false );
 		}
 	}