-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
ExecutePatchtAsync #1948
Comments
I bet you just need some overloads. Please feel free to open a PR to add them. These are basically copy-pasting from those you mentioned, like this:
I would say that "impossible" is an overstatement as |
Same goes for ExecuteDeleteAsync. |
I would greatly appreciate it if you guys submit PRs adding two LoC plus the XML comment for each of those missing extensions. |
@alexeyzimarev Can I add them |
To be honest, I would be happy to:
OR
It happened to me few times, that I used on request ExecutePostAsync but client for set to GET and it was really hard for me to notice that, because server behaved somehow correctly. |
Could you elaborate? Do you mean you created a GET request and used |
Of course |
yes. Just copy & paste * change only Execute. It happened to me pretty often. |
@alexeyzimarev #1996 please review the PR. |
Fixed in #1996 |
Is not possible to call method PATCH wihout throwing an exception when request was not successful.
Basically I'm missing the same funcionality as there is for GET, POST, PUT and DELETE methods.
The text was updated successfully, but these errors were encountered: