fix(http): include transferCache when cloning HttpRequest#54939
fix(http): include transferCache when cloning HttpRequest#54939mlz11 wants to merge 2 commits intoangular:mainfrom
Conversation
b07fbb4 to
f829824
Compare
6b9a647 to
12b50df
Compare
alan-agius4
left a comment
There was a problem hiding this comment.
Thanks for this.
Can you please update the commit message scope from common to http?
12b50df to
6f244fc
Compare
Thanks @alan-agius4 for the quick review 🙂 |
6f244fc to
8a90bb8
Compare
alan-agius4
left a comment
There was a problem hiding this comment.
LGTM, thanks for your contribution
|
Can you please run update the golden files via |
Fixes a bug where HttpRequest.clone() does not include the transferCache property. Fixes #54924.
Refactor how boolean options are handled in HttpRequest.clone() method by using nullish coalescing operator
8a90bb8 to
89e3d25
Compare
Of course, done ✅ |
| const responseType = update.responseType || this.responseType; | ||
|
|
||
| // Carefully handle the transferCache to differentiate between | ||
| // `false` and `undefined` in the update args. |
There was a problem hiding this comment.
now it also handles null so mayby add that to comment : undefined or null here and in other places that were edited. Also why not add move this logic together with withCredentials and reportProgress? becouse now
this comment is duplicated in lines 485 and 495
dylhunn
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
jessicajaniuk
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
atscott
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
|
This PR was merged into the repository by commit b80434a. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Fixes #54924.
What is the new behavior?
Does this PR introduce a breaking change?
Other information