Compatibility Issue with Zf2Whoops module

[Devidia]

The match route does not works when we using the Zf2Whoops module.

[RWOverdijk]

That's a shame. We're waiting until the absolute last moment to figure out if the request was for an asset. Unless we work around their priority it would seem modules are simply not compatible.

[Ocramius]

By the way - why does the whoops module intercept 404s? Shouldn't it just
handle 5xx exceptions?
On 30 May 2013 13:36, "Wesley Overdijk" notifications@github.com wrote:

That's a shame. We're waiting until the absolute last moment to figure out
if the request was for an asset. Unless we work around their priority it
would seem modules are simply not compatible.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/90#issuecomment-18674957
.

[Devidia]

No, 404 also.

[Ocramius]

@Devidia and there you got your problem ;) Either Whoops stops handling 404s or AM cannot kick in :)

I honestly don't think 404s should be stopped from bubbling up.

[Devidia]

I just wanted to share this information with you. Might be, it's a good idea to put a "Warning" about that in your tutorial. Because, I spent many time to understand this compatibility issue. that's it.

Anyway, thank you for your good job.

[Ocramius]

@Devidia well, you could consider adding a conflict section to composer.json in their repo until they fix it (not here, it's not an issue of this module IMO)

@RWOverdijk could be closed

@Devidia please bring it up on Zf2Whoops with the considerations collected here.

[RWOverdijk]

@Ocramius We could change the priority. So if we can't find anything, maybe they can then catch the 404. Then they would play nice together.

[Ocramius]

@RWOverdijk I don't think it has to be handled here. Zf2Whoops should still let the exception reach the application.finish

[RWOverdijk]

We should at least let them know this issue exists, no?

[Ocramius]

@RWOverdijk opened ghislainf/zf2-whoops#2 - this one can be closed

[ghislainf]

The module is fixed, it do not intercepts the 404 now. @Ocramius you're right, it was no any interest.

[Ocramius]

@ghislainf thanks!