Still problem with file system.

[alextech]

1. Getting same error with latest flysystem in actual project

Attempted usage:

throw Fault::exception(\Importer\ImporterException::class, 'Problem selecting sheet', 1002, $e);

2. It is writing to _compiled under omegad-biz. That is a problem, because hosts will not have write permissions there. Write permissions will be often given manually to designated directory, such as data at top level.

[panosru]

I messed up the commit issue reference, the above commit is referring to issue #7, so we continue there.

[panosru]

@alextech the package by default uses the _compiled directory which is inside the package.

In the case that write permissions are not enabled then you can use Fault::setCompilePath('/my/path'); before executing any other Fault::* methods.

let me know if that solves your issue

Description

---

public void \Omega\FaultManager\Fault::setCompilePath ( string $path )

[panosru]

also please note that throw Fault::exception(\Importer\ImporterException::class) won't work as namespaces are not yet supported.

Actually now that I tested it, it will break your application if you use namespaces because it will create a path _compiled/Importer/ImporterException.php and next time you will run your app you will receive errors like

Notice: Undefined index: extension in ...

Fatal error: Uncaught TypeError: strcmp() expects parameter 2 to be string, null given in ...

I probably have to add a check for that or implement namespaces.

[panosru]

@alextech please run composer update omegad-biz/fault-manager for now. This concept is something discussed in #4 but not yet implemented.

[alextech]

\Omega\FaultManager\Fault::setCompilePath(__DIR__.'/../data/exceptions');

has no effect. New classes are still created in vendor.

[panosru]

Let me know where you place the above code as I just checked and it works on my side.

Remember, Fault is a static class so setCompilePath needs to be called before Fault::exception or Fault::throw in order to be taken into account.

[alextech]

Sorry, I forgot my unit tests, do not go through entire pipeline initialization code, where I put that function. I will have to add this to application configuration service in a way that it is applied in all places on my end.

[panosru]

You can change your path everywhere and anytime you need.

For instance:

Fault::setCompilePath('/my/path');
Fault::exception('MyCustomException'); // compiled file will be under /my/path
Fault::setCompilePath('/my/other/path');
Fault::exception('MyOtherCustomException'); // compiled file will be under /my/other/path
// etc...

For unit testing you can have something like that:

/**
 * @before
 */
protected function setTestPath(): void
{
    Fault::setCompilePath('/my/testing/path');
}

Code example

[panosru]

In addition to the above example, my mistake is that I forgot to append front-slash at the end of the path so /my/path should be /my/path/.

I probably need to have a check for that and in a case is missing to append a trailing front-slash to the path.