This is just a quick post sharing something I was able to figure out after doing some research.

The situation: our application throws exceptions by means of “talking back to the user”.
As developer we don’t want to be notified about all these exceptions.
They aren’t as important as any other exception that should be considered “critical”.
Still, we do want to find these exceptions in the logs, because they can sometimes provide valuable feedback about the usability of the system.

So basically we just want Symfony to log the exception, but dial the standard log level “critical” for certain types of exceptions down to “info”.
Monolog has the concept of a processor for that (represented by the optional ProcessorInterface).
The implemented process() method should return the modified log record, which is actually an array containing the different parts of a log record (the level, the message, and the context).
Since not every log record is related to an exception, we don’t have to do anything in most cases.
Here’s the code:

use Monolog\Logger;
use Monolog\Processor\ProcessorInterface;
use Symfony\Component\HttpKernel\EventListener\ErrorListener;
use Symfony\Component\HttpKernel\Exception\HttpExceptionInterface;
use Throwable; final class AdjustLogLevelForExceptions implements ProcessorInterface
{ public function __invoke(array $record): array { if (!isset($record['context']['exception'])) { /** * Symfony's ErrorListener will provide a Throwable through the log message's context. * If the context has no "exception" key, we don't have to further process this log record. * * @see ErrorListener::logException() */ return $record; } $throwable = $record['context']['exception']; if (!$throwable instanceof Throwable) { // For some reason the provided value is not an actual exception, so we can't do anything with it return $record; } // Change the log level if necessary $modifiedLogLevel = $this->determineLogLevel($throwable, $record['level']); $record['level'] = $modifiedLogLevel; $record['level_name'] = Logger::getLevelName($modifiedLogLevel); return $record; } private function determineLogLevel(Throwable $throwable, int $currentLevel): int { if ($throwable instanceof UserErrorMessage) { // These are exceptions that will be rendered to the user. return Logger::INFO; } return $currentLevel; }
}

Now you only have to register this processor as a service and tag it as monolog.processor:

services: AdjustLogLevelForExceptions: tags: - { name: monolog.processor }

If you use auto-wiring and have set up auto-configuration for the directory where the AdjustLogLevelForExceptions is located you don’t even have to tag this service.
The MonologBundle should automatically do that for you.

In our last episode, we discussed coming improvements to PHP’s type system. Today we look at a new construct that makes branching logic more powerful.
PHP has had a switch statement since the dawn of time, modeled on the same construct in C. You’ve surely seen it before:
<?php switch ($var) { case 'a': $message = “The variable was a.”; break; case 'b': $message = “The variable was c.”; break; case 'c': $message = “The variable was c.

This episode is sponsored by
RingCentral Developers

The post Interview with Oliver Davies appeared first on Voices of the ElePHPant.

In this blog, we walk through how to set up a basic php web server with Swoole.

Truncated by Planet PHP, read more at the original (another 23160 bytes)

The PHP team is pleased to announce the seventh testing release of PHP 8.0.0, Beta 4. This point in the release cycle would normally be RC1, however we’re still finalizing development of the JIT and squaring away named arguments, so we’ve opted for an extra beta release with plans to start the RC cycle in two weeks. At this time, we’re not planning to adjust the GA date, however this may change during the course of the RC cycle. The updated release schedule can, as always, be found on the PHP Wiki. For source downloads of PHP 8.0.0 Beta 4 please visit the download page.Please carefully test this version and report any issues found in the bug reporting system.Please DO NOT use this version in production, it is an early test version. For more information on the new features and other changes, you can read the NEWS file, or the UPGRADING file for a complete list of upgrading notes. These files can also be found in the release archive. The next release will be the Release Candidate 1, planned for Oct 1 2020.The signatures for the release can be found in the manifest or on the QA site.Thank you for helping us make PHP better.