Skip to content
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

Switch back to whatwg-fetch #235

Merged
merged 2 commits into from
Jan 2, 2019
Merged

Conversation

xg-wang
Copy link
Member

@xg-wang xg-wang commented Sep 14, 2018

JakeChampion/fetch@141665b...master
2 changes worth notice due to fetch spec change:
JakeChampion/fetch#651 JakeChampion/fetch#640

@@ -15,8 +15,7 @@ var FakeXMLHttpRequest = appearsBrowserified ? getModuleDefault(require('fake-xm
self.FakeXMLHttpRequest;

// fetch related ponyfills
// TODO: use whatwg-fetch once new version release
var FakeFetch = appearsBrowserified ? getModuleDefault(require('@xg-wang/whatwg-fetch')) : self.WHATWGFetch;
var FakeFetch = appearsBrowserified ? getModuleDefault(require('whatwg-fetch')) : self.WHATWGFetch;

Choose a reason for hiding this comment

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

I noted in #221 thinking that it's a documentation bug, but self.WHATWGFetch is undefined for me.

@xg-wang
Copy link
Member Author

xg-wang commented Oct 3, 2018

@rwjblue @stefanpenner need review

@xg-wang
Copy link
Member Author

xg-wang commented Oct 7, 2018

@stefanpenner Do you think we should check the import of FakeFetch to avoid the breaking upgrade like #221 ?

jherdman added a commit to jherdman/ember-cli-mirage that referenced this pull request Oct 9, 2018
This change does not, like originally intended, make Pretender a peer
dependency. There's a lot of work and debate being done here, so in the
mean time let's unlock `fetch` support in Mirage.

Dependency changes
------------------

* pretender 1.6 => 2.1. I've locked at 2.1.0 until
  pretenderjs/pretender#235 is resolved. This will require code changes
  on our end, and thus I don't want this sliding from underneath us and
  causing unnecessary weeping and gnashing of teeth.
* Add xg-wang/whatwg-fetch. Required for the upgrade.
* fake-xml-http-request 1.4.0 => 2.0.0. Required for the upgrade.
* route-recognizer 0.2.3 => 0.3.4. Required for the upgrade.
* ember-cli-node-assets 0.1.4 => 0.2.2. Because why not! I'm kneed deep
  in this stuff, so I may as well keep this up to date.
@xg-wang
Copy link
Member Author

xg-wang commented Oct 9, 2018

yarn link "pretender" on ember-cli-mirage and all tests pass.
So that we won't break pretender 1->2 upgrade. See miragejs/ember-cli-mirage#1389 for some usecase discussion.

@xg-wang
Copy link
Member Author

xg-wang commented Nov 10, 2018

Anything need to do to get this merged?

givanse added a commit to givanse/pretender that referenced this pull request Jan 1, 2019
givanse added a commit to givanse/pretender that referenced this pull request Jan 1, 2019
@mike-north mike-north merged commit 2b25081 into pretenderjs:master Jan 2, 2019
@xg-wang xg-wang deleted the upgrade branch January 2, 2019 16:47
@mike-north mike-north mentioned this pull request Jan 2, 2019
2 tasks
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.

4 participants