Kirk Madera

Replace Submodules with Composer

1

The module currently halfway uses submodules and Composer. It would be helpful to move entirely to Composer.

We noticed an "Array to string conversion" bug with some of our queries. Not sure if we made the right fix, but we ended up overriding a few classes in...

Namespace conflict with webonyx/graphql-php

4

`webonyx/graphql-php` is a popular PHP GraphQL server library. I was going to use this module until I discovered that it uses the namespace GraphQl and directly conflicts with `webonyx/graphql-php`. Any...

Adds explicit setup instructions to address #52

5

This addresses specific issues I ran into while setting this VM up in order to prevent other users from getting stuck on them.

To make this more accessible, we should add more detailed instructions on how to set up the VM using Vagrant along with common pitfalls. I ran into an issue that...

newrelic_ini_appname does not make it into newrelic.ini (and presumably other vars)

6

The [newrelic.ini](https://github.com/fsalum/puppet-newrelic/blob/master/templates/newrelic.ini.erb) template attempts to use data with local variable names, but no data is actually being passed to it. I believe that all parameters in the [php agent definition](https://github.com/fsalum/puppet-newrelic/blob/master/manifests/agent/php.pp#L37)...

Passed newrelic::agent::php args down to newrelic::php::newrelic_ini

2

Passed newrelic::agent::php args down to newrelic::php::newrelic_ini so that the newrelic.ini template has access to the data. I confirmed that the data makes it to the template correctly now.

Hydrate/extract changes value when there are consecutive underscores

1

### Bug Report | Q | A |------------ | ------ | Version(s) | 4.15.0 #### Summary #### Current behavior Extract/hydrate should be symmetrical. Extracting, then hydrating any value should produce...

The docs frequently state the use of OpenSwoole\Coroutine::run. See https://openswoole.com/docs/modules/swoole-coroutine. Yet, I don't see it as part of this package. Is this an oversight? Are the docs just out of...

TaskEventDispatchListener DI loop

3

### Bug Report I am following the [recommended way to run a task event listener](https://docs.mezzio.dev/mezzio-swoole/v4/async-tasks/#queueing-task-data-for-the-taskeventdispatchlistener), using a `TaskEventDispatchListener`, but have run into a DI loop. `Mezzio\Swoole\Task\TaskEventDispatchListener` > `Mezzio\Swoole\Event\EventDispatcherInterface` > `Mezzio\Swoole\Event\SwooleListenerProvider`...