fix: Fetch handler hacks for Mirage #9199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
store.request
to be intercepted by Miragefetch
until after EmberData closes overfetch
.cloneResponse
for Mirage mock responsesResponse.body
, which is required forcloneResponse
. SincecloneResponse
only exists because updating the headers on a realResponse
isn't allowed (but Mirage also--conveniently--doesn't implement this limitation), we can just update the headers on the Mirage mock response instead.Notes for the release