help to deal with exceptions and logger

Question

help to deal with exceptions and logger

Sa1ch Feb '20

Created Feb '20	Last Reply Feb '20	Replies 2	Views 169	Votes 0

Sa1ch 4.3k

Feb '20

I have declared the logger via DI

$di->set( 'logger', function () use ($config) {

    $fileNameMain = strtr($config->logger->fileNames->cli->main, ['[%date%]' => date('Y-m-d')]);
    $fileNameEaisto = strtr($config->logger->fileNames->cli->eaisto, ['[%date%]' => date('Y-m-d')]);
    $adapterMain = new Stream($fileNameMain);
    $adapterEaisto = new Stream($fileNameEaisto);

    $logger = new Logger(
        'messages',
        [
            'main' => $adapterMain,
            'eaisto' => $adapterEaisto
        ]
    );

    return $logger;
}

);

and there is a class for handling exceptions:

namespace App\Services\Exceptions;

class EaistoException extends \Exception { public function __construct($msg){ $this->logger->critical($msg); } }

How do I pass the exception object to the logger? The above code causes an error:

Undefined property: App\Services\Exceptions\EaistoException::$logger

sorry for the stupid question :)

Lajos Bencz
77.7k

Accepted
answer

edited Feb '20
Feb '20

A very simple example. though not quite what i was talking aboug:

abstract class LoggingException extends \Exception {
    const LOGGER_SVC = 'logger';

    public function __construct($message='', $code=0, $previous=null) {
        $di = \Phalcon\Di\FactoryDefault::getDefault();
        $logger = $di->getShared(self::LOGGER_SVC);
        $logger->critical($message);
        parent::__construct($message, $code, $previous);
    }
}

The caveat is that this will always use the globally set default di - you cannot specify your own.

Lajos Bencz · Answer 1 · 2020-02-25T05:01:08-07:00

You would have to create a base Exception class that is Phalcon\Di\Injectable, and then inherit all your errors from there, that way the Exception will have a logger property.

The tricky part is that you must inherit from either \Throwable or \Exception, so you must implement your own Injectable methods (setDI, getDI, __get).

Sa1ch · Answer 2 · 2020-02-25T23:33:16-07:00

You would have to create a base Exception class that is Phalcon\Di\Injectable, and then inherit all your errors from there, that way the Exception will have a logger property.

The tricky part is that you must inherit from either \Throwable or \Exception, so you must implement your own Injectable methods (setDI, getDI, __get).

thanks! maybe you have an example? I will be very grateful to you.

Sa1ch · Answer 3 · 2020-02-26T07:50:04-07:00

A very simple example. though not quite what i was talking aboug:
abstract class LoggingException extends \Exception {
  const LOGGER_SVC = 'logger';

  public function __construct($message='', $code=0, $previous=null) {
      $di = \Phalcon\Di\FactoryDefault::getDefault();
      $logger = $di->getShared(self::LOGGER_SVC);
      $logger->critical($message);
      parent::__construct($message, $code, $previous);
  }
}
The caveat is that this will always use the globally set default di - you cannot specify your own.

thanks! I have a couple of days will return to this issue, I try your example. you helped me.