Skip to content

Small refactor to XHR assertSuccess#7140

Closed
jridgewell wants to merge 1 commit intoampproject:masterfrom
jridgewell:xhr-refactor-assertSuccess
Closed

Small refactor to XHR assertSuccess#7140
jridgewell wants to merge 1 commit intoampproject:masterfrom
jridgewell:xhr-refactor-assertSuccess

Conversation

@jridgewell
Copy link
Copy Markdown
Contributor

Makes it sync if possible, and un-nests a bit.

Makes it sync if possible, and un-nests a bit.
@jridgewell jridgewell requested a review from dvoytenko January 20, 2017 23:49
* Returns the response if successful or otherwise throws an error.
* @param {!FetchResponse} response
* @return {!Promise<!FetchResponse>}
* @return {!FetchResponse|!Promise<!FetchResponse>}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this a very strange response type? I realize that in a promise chain this doesn't matter, but we should at least rename this method to avoid accidents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants