Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Consider removing the new trigger_error deprecation warnings #12973

Closed
@weaverryan

Description

@weaverryan

Hi guys!

I know we just started adding them, but I wanted to have a conversation about the deprecated warnings being added to 2.7. There have been several issues where the warnings are causing bad behavior (e.g. many systems map all errors to exceptions).

@dbu just talked about this at #12945 (comment), and I agree that it's a BC-ish break. I'm also worried about people getting their error logs filled up with warnings (we can't control what level their logging on production) - e.g. 10 GB log file that fills up the disk space and ends up being Symfony's fault :).

The downside is that we lose this cool way of auto-detecting that you're using deprecated stuff, and I'm not sure if there's a way to keep that.

Ref #12945, #12868, phpspec/phpspec#580, https://twitter.com/lsmith/status/543755471853993986

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions