Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@anaisbetts
Copy link
Member

This PR adds the code to issue REST requests, which is surprisingly complicated. Based on the return value of the method, they could want:

  • A deserialized JSON object (i.e. Task<Toaster>)
  • A completion result (e.g. if it's a delete, so Task)
  • The resulting data as a string (i.e. Task<string>)
  • The actual response object (i.e. Task<HttpResponseMessage>)
  • All of those things except for completion, for Rx too

anaisbetts pushed a commit that referenced this pull request Jul 23, 2013
Handle actually issuing REST requests, not just building them
@anaisbetts anaisbetts merged commit f2c5dbe into master Jul 23, 2013
clairernovotny pushed a commit that referenced this pull request May 7, 2019
clairernovotny pushed a commit that referenced this pull request Jun 5, 2019
@lock lock bot locked and limited conversation to collaborators Jun 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants