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

Add option to use default HTTP status codes as response #34

Closed
marcominerva opened this issue Mar 6, 2023 · 0 comments · Fixed by #35
Closed

Add option to use default HTTP status codes as response #34

marcominerva opened this issue Mar 6, 2023 · 0 comments · Fixed by #35
Assignees
@marcominerva
Labels
enhancement New feature or request

Comments

@marcominerva
Copy link
Owner

Currently, OperationResults.AspNetCore and OperationResults.AspNetCore.Http require a mapping from generic FailureReasons to actual HTTP status codes. This is done to guarantee complete decoupling. However, in certain scenarios it could be useful to directly use original HTTP status codes.

In order to support this use case, a new property must be added to OperationResultOptions so that the library can be instructed about mapping behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marcominerva marcominerva

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add option to directly use HTTP status codes as failure reasons marcominerva/OperationResults
1 participant
@marcominerva