BaseErrorClass ChaliceViewError- returns a status code of 500

I know this issue isn't likely to be addressed as ChaliceViewError is a base/default error type for the generic ootb exception handling, but In my use case i wanted to throw a InternalServer Error (500) , and had to build out new class just for that, and feel like that should be the defacto behaviour when one encounters an 'unexpected' issue executing a server response to a route invocation.... I believe especially if the API is exposed publicly... we want to let end users know the issue is 'on the server/api side' but we don't want to expose the framework used to build the API, its generally a recurring security concept in Web app/API interaction.

Maybe what i'm asking for is why not stick to standard http error types... if anything this helps keep API developed RFC compliant?

Happy just to understand the reasoning behind the ChaliceViewError usage instead.

The issue names ChaliceViewError but no files or tests. Start by locating ChaliceViewError and the existing HTTP exception handling, then clarify whether the default response should be HTTP 500 without exposing framework details. Done requires an agreed behavior and corresponding tests or documentation.

Written by the indexing model from the issue text.