Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.
This repository was archived by the owner on Jan 30, 2020. It is now read-only.

ExceptionHandler trace args size problem #16

Description

@Ragazzo

Currently there is a problem with print_r in ExceptionHandler formatter, if argument is an object and not simple POCO / DTO but one that contains links to other objects and so on, it becomes very not trivial to dump exception message.

For example, with DoctrineModule, DoctrineORMModule configured in application if i make test exception throw in onBootstrap of module throw new Exception('Evil exception occured'); then the only argument of first trace will be MvcEvent but since it contains information about a lot of in application my memory limit is not enough to log exception, even 512 Mb not enough to log exception.

Possible solution:

would be greate to introduce to ExceptionHandler attribute like traceArgumentLevel that will dump object only to needed level as Doctrine2 Debug::dump does.

@Maks3w what your thoughs on this one?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions