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 new method to KiwiStandardResponses for creating a "standard" 500 error #1164

Closed
sleberknight opened this issue Jul 22, 2024 · 0 comments · Fixed by #1182
Closed

Add new method to KiwiStandardResponses for creating a "standard" 500 error #1164

sleberknight opened this issue Jul 22, 2024 · 0 comments · Fixed by #1182
Assignees
Labels
new feature A new feature such as a new class, method, package, group of classes, etc.
Milestone

Comments

@sleberknight
Copy link
Member

sleberknight commented Jul 22, 2024

KiwiStandardResponses contains a standardErrorResponse(Response.Status status, String errorDetails) method which requires specifying the response status. This becomes tedious when you simply want to create a "default" 500 error.

This issue adds a new method which will create a new Response with status code 500 Internal Server Error and the given error details. The signature is:

Response standardInternalServerErrorResponse(String errorDetails)

There should also be a method that returns a Response.ResponseBuilder.

@sleberknight sleberknight added the new feature A new feature such as a new class, method, package, group of classes, etc. label Jul 22, 2024
@sleberknight sleberknight added this to the 4.3.0 milestone Jul 22, 2024
@sleberknight sleberknight self-assigned this Aug 9, 2024
sleberknight added a commit that referenced this issue Aug 9, 2024
* Add standardInternalServerErrorResponse
* Add standardInternalServerErrorResponseBuilder

Closes  #1164
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature A new feature such as a new class, method, package, group of classes, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant