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.

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

Add deprecation warning to 404/5xx middleware #361

Merged
merged 1 commit into from
Apr 8, 2015

Conversation

jasisk
Copy link
Member

@jasisk jasisk commented Apr 7, 2015

These middleware cause more problems than they solve.

Because they're everywhere, I'd like to keep them in place for another
major. The default express handler is sufficient in many cases. This is
more a documentation issue than anything else (and one we've already
addressed in the generator).

Closes #359.

These middleware cause more problems than they solve.

Because they're everywhere, I'd like to keep them in place for another
major. The default express handler is sufficient in many cases. This is
more a documentation issue than anything else (and one we've already
addressed in the generator).

Closes #359.
@jasisk jasisk self-assigned this Apr 7, 2015
@jasisk jasisk added this to the 2.0.0 milestone Apr 7, 2015
@aredridel
Copy link
Contributor

Awesome. 👍

@grawk
Copy link
Member

grawk commented Apr 7, 2015

👍

jasisk added a commit that referenced this pull request Apr 8, 2015
Add deprecation warning to 404/5xx middleware
@jasisk jasisk merged commit 44cfa7a into v2.x Apr 8, 2015
@jasisk jasisk deleted the middleware-warn-deprecation branch April 8, 2015 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deprecate shipped 404 and 500 middlewares
4 participants