You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will have two paths: jQuery.ajax which will require najax and a new, opt-in ember-fetch backend which have built in FastBoot support and do not require najax.
I don't think we can/should drop MonkeyPatch™ from ember-cli-fastboot right away because of support for older ED. But I am interested to hear what would be an acceptable time frame for doing it (@rwjblue)?
The text was updated successfully, but these errors were encountered:
I am not sure what the motivation is behind adding the patching in ember-data itself. It should be agnostic to all this. Please see my reasoning on your PR.
Ultimately it is odd that this addon is coupled in any way to ember-data. Ideally, fastboot provides capabilities that are used by other addons to get their jobs done. The current path (encoding non-fastboot addon logic in ember-cli-fastboot) is not scalable...
The ember-data team is working to move away from the $.ajax style of request (towards using ember-fetch), and having ember-data “own” this particular aspect makes it easier for it to massage the migration story.
We are adding direct support for
FastBoot
in Ember Data.emberjs/data#5385
We will have two paths:
jQuery.ajax
which will requirenajax
and a new, opt-inember-fetch
backend which have built inFastBoot
support and do not requirenajax
.I don't think we can/should drop MonkeyPatch™ from
ember-cli-fastboot
right away because of support for olderED
. But I am interested to hear what would be an acceptable time frame for doing it (@rwjblue)?The text was updated successfully, but these errors were encountered: