-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Move EmptyHttpResult to Http.Abstractions #46077
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
Conversation
This change resolves: #41330 Overall, I'm fine with moving only the problematic type lower. I don't think there's other HttpResult types that need the same treatment. Does this need an API review or does the type forward mitigate that? |
From the user's perspective, nothing changes. Doesn't seem necessary. What do you think @halter73? |
This is a nonbreaking change that doesn't really add API. I don't think we have to API review type forwards. The only thing to discuss would be the assembly to move it to. I think normal PR review is sufficient. |
Numbers!
And no more warnings from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
This PR moves
EmptyHttpResult
to abstractions and adds a type forward. This allows us to no longer require reflection hacks to get a reference toEmptyHttpResult.Empty
.IMO this isn't just a change to make our code better. It is normal to have a "null" or "empty" value/implementation be part of the abstraction.