fetch() should return asynchronous promises.

Question

fetch() should return asynchronous promises.

Opened this issue 11 years ago · 4 comments

Answer 1 · 2014-04-09T03:22:19.000Z

👍

It would be nice if the promise returned by fetch resolves to the populated model, so workarounds like http://stackoverflow.com/a/17643647/476712 are no longer required.

Answer 2 · 2014-04-09T17:58:08.000Z

We hear you, and we're working on it! We're going to add a find() method that resolves with the populated model. Work in Progress can be found here: #76

We're currently in the process of doing some maintenance: migrating to a Broccoli build system #85 and releasing a stable 2.0 release.

Once that is done, we have this addition and more coming soon! (:

Answer 3 · 2014-04-10T05:56:11.000Z

Thank you. Looking forward to the 2.0 release.

On Wed, Apr 9, 2014 at 11:28 PM, Josh Lubaway notifications@github.comwrote:

We hear you, and we're working on it! We're going to add a find() method
that resolves with the populated model. Work in Progress can be found here:
#76 #76

We're currently in the process of doing some maintenance: migrating to a
Broccoli build system #85 https://github.com/zendesk/ember-resource/pull/85and releasing a stable
2.0 release.

Once that is done, we have this addition and more coming soon! (:

Reply to this email directly or view it on GitHubhttps://github.com//issues/77#issuecomment-39995826
.

Answer 4 · 2014-04-15T17:57:28.000Z

@lorefnon Ember Resource 2.0 has been released. We have been running it in production for a while now, so I am comfortable saying it is production ready ;)

Now, we will begin work on Ember Resource 3.0 which means we can make breaking changes -- like dropping Ember 0.9.x support. There is currently no planned date for 3.0, but we will keep moving forward and start adding features like these to the master branch!