Add a generic error view handler

[coolbootscoder]

Code of Conduct

• I agree to follow Django's Code of Conduct

Feature Description

This proposal recommends adding a generic error view handler, refactor existing code to build around this generic handler and allow for error handling views for errors (4xx and 5xx) that are currently not supported.

Problem

Currently there are a handful of error views that can be overridden with custom views (see: https://docs.djangoproject.com/en/dev/ref/views/#error-views). To add new error handler views for other error codes (like 413 see: https://code.djangoproject.com/ticket/35281) requires the ticket and PR process. A generic handler would allow for any currently unsupported error code to be handled with a custom view.

Request or proposal

request

Additional Details

The conversation on the PR is where the idea of refactoring the error view comes from: https://github.com/django/django/pull/17960/files.

This PR was a work in progress on an idea for a generic handler: django/django#18725

Implementation Suggestions

No response

[github-actions]

Thank you coolbootscoder for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.

Community instructions

For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"

Reaction Guide

• 👍 This is something I would use
• 👎 This is something that would cause problems for me or Django
• 😕 I’m indifferent to this
• 🎉 This is an easy win