ghislainf / zf2-whoops Goto Github PK

I don't want to load this module on production so...

Is there a way to not display environment variables?

Hi,

Using in composer.json requirement:

"zendframework/zendframework": "2.*"

Causes to install lot of unnecessary libs but only that your module need are defined in your Module.php

use Zend\EventManager\EventInterface;
use Zend\ModuleManager\Feature\BootstrapListenerInterface;
use Zend\Console\Request as ConsoleRequest;
use Zend\Stdlib\ResponseInterface as Response;
use Zend\Mvc\Application;
use Zend\Mvc\MvcEvent;

So I think, that this configuration will fit enough, and do not clutter someone else configuration.

"zendframework/zend-mvc": "2.*",
"zendframework/zend-modulemanager": "2.*",
"zendframework/zend-loader": "2.*",
"zendframework/zend-config": "2.*",

Hi, please start tagging this module.
Thanks to this using the composer is stressless.

Hey there,

yesterday i tried to use this module with PHP7.
Unfortunately it doesn't work that well. The TypeHint for the expected \Exceptions don't work for the raised new \Error types.

Are you fixing this already? If not, maybe i can look into it.
Greets :)

As discussed on RWOverdijk/AssetManager#90, the current ZF2Whoops module implementation also catches 404 errors with no exception.

That makes the module unusable with AssetManager.

Possible fixes:

• Let the error untouched as long as there is no exception parameter
• Set a flag for incompatibility with AssetManager in composer.json

After updating this module today, it refused to work - I'm getting following error:

Module (Zf2Whoops) could not be initialized.

Looks like it happens because autoloader information was removed from composer.json file. What was the reason behind it? And how to make it work again? :)

Hi, how to handle checked exception, like BjyAuthorize\Exception\UnAuthorizedException?

It would be really nice to have logger support.

In production errors are not shown to users, but they still should be logged. It would be really nice to log whoops output and of course exception data using Zend\Log\Logger

Logger could be passed in as a dependency (via setLogger method).

This code hasn't changed in quite a while but a release hasn't been tagged since 2013; it would be nice if we had a released version we could pin in composer.json instead of relying on dev-master. Is there any reason we can't do this? If there are known issues holding up a release, I'd be willing to contribute some time to help resolve them.

https://github.com/ghislainf/zf2-whoops/blob/master/composer.json#L30

Dependencies will force a full framework download. It'd be necessary to limit it to those components you need.

Thanks!