QUIQQER Composer Events
======

<center>
![](https://github.com/QUIQQER/composer/raw/master/bin/images/Readme.jpg)
</center>

#### Repository

- https://github.com/QUIQQER/composer

### New Features
#### What feature(s) did you add?

Composer is in the PHP world what NPM is in the nodejs world. QUIQQER has therefore been building on Composer since its beginnings and has it deeply integrated. So that the integration works over the web and over the console we have built a bridge which can communicate between CLI and web.

The problem was, a direct output was made on the console and therefore it could not be intercepted. In some cases you might want to log the output or continue working with it. To solve this problem we implemented Symfony Process Handling and integrated an Event Handling.

Now it is possible to react to the output event and continue working with the output.

```
<?php

require 'vendor/autoload.php';

$Composer = new QUI\Composer\Composer(dirname(__FILE__));
$Composer->addEvent('onOutput', function ($self, $output, $type) {
    echo $output;
});

$Composer->getOutdatedPackages();
```


#### How did you implement it/them?

Commits: [843eb93](https://github.com/QUIQQER/composer/commit/843eb930aaf01aa51d34c166cadc2a605d7cccd9) [93649c0](https://github.com/QUIQQER/composer/commit/93649c0b973e17eb2440ca6eb5e4a96e1199dfa6) [f42ac7a](https://github.com/QUIQQER/composer/commit/f42ac7a2d05baaa9c6796445061ddab446676da7) [920a50e](https://github.com/QUIQQER/composer/commit/920a50ec5446beb1c03021ac0cba9eb088bcf1fe) [6bed09](https://github.com/QUIQQER/composer/commit/6bed0952baf7a3ef59db5a971ea95598cfdaffa7)

So that the Composer class can fire events at all, a completely new event class was introduced.

https://github.com/QUIQQER/composer/commit/843eb930aaf01aa51d34c166cadc2a605d7cccd9#diff-cf146ce40cbf85c9b5cf8766c4e19d76

Afterwards this event class was integrated in all three composer classes, main Composer class, CLI class and the Web class.

![](https://cdn.steemitimages.com/DQmYBM89LuQtQy832v9LA1wP2Dq6r9kEzgmeJRwV7btbPMF/image.png)

An `addEvent` method was introduced so that the event can also be registered on the Composer instance. The same procedure was used in the main Composer class and in the Web composer class.

![](https://cdn.steemitimages.com/DQmcQVvNjPoZvzzhuBftK2rNCgYsLVMH7xXdsUNd8wJYjZr/image.png)

Now that all three installation classes have the event handling integrated, it is possible to react to the `onOutput` event (in the theory). For the whole thing to work the `output` event has to be executed as well.

The CLI it is a little bit tricky and not so simple, because the output is a direct output. This meant that some changes had to be made here. Symfony offers a good process class which executes a CLI command and the output can be intercepted on the fly. I.e. all system commands had to be started with such a process.

In order for the whole thing to work, we have centrally introduced a method which implements such a procedure.

![](https://cdn.steemitimages.com/DQmXLvGRR283mumuRQPvLwmHe4LP2N89RWoaqjJUDiayWN1/image.png)

After all commands were adjusted, the integration of the event handling was perfect.

![](https://cdn.steemitimages.com/DQmTBJenTfLxwKDkVqS32Pk34CbyNpfauFNRj3Ckw2YPe9h/image.png)

Logging is now no longer a problem and also further handling with the output can be managed. With this feature QUIQQER has taken another step towards version 1.3.

Thanks for reading,
Hen, for PCSG Developers


#### GitHub Account

- https://github.com/dehenne