Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle deprecated errors #100

Closed
denis-sokolov opened this issue Oct 14, 2013 · 2 comments
Closed

Handle deprecated errors #100

denis-sokolov opened this issue Oct 14, 2013 · 2 comments
Milestone
1.2.0

Comments

@denis-sokolov
Copy link
Collaborator

Usually E_DEPRECATED and E_USER_DEPRECATED do not require immediate action, and as such, it would be great if handlers would not handle them by default, and we had a DeprecatedHandler which ideally would just send an email to developers, and also allow muting certain errors as a way to temporarily postpone fixing.
@denis-sokolov
Copy link
Collaborator Author

Refactoring small time ideas like this one into a wiki page.

@denis-sokolov denis-sokolov mentioned this issue Dec 15, 2013
Closed
@denis-sokolov
Copy link
Collaborator Author

Also see #118 for ramblings on topic.

denis-sokolov added a commit that referenced this issue Feb 16, 2014
@denis-sokolov
PrettyPageHandler: remove deprecated notices
d6dcec2 
Until we handle deprecated errors in a graceful manner,
triggering this aborts the application, which defeats the purpose of compatibility.
Also see issue #100.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.2.0
Development

No branches or pull requests
1 participant
@denis-sokolov