store.findOne ? about data

[pixelcort]

I would like to see this as well.

Workaround is to observe the array and take its firstObject once it comes in.

[garth]

How about adding a wrapper for findMany that returns a single object without ID, so that you can push it into the view immediately, then hold a reference to it until the ajax callback and populate with the first record returned.

The key issue for me is not having to manage the callbacks (plumbing) in my app logic.

[wycats]

Is the rationale for this feature a singleton resource in general?

[garth]

I think that there are lots of cases where I want to get one instance of a model and I know it's there but I don't know the ID.

For example: in a calendar system I may want to get today or this month, I know they exist (and if they don't I will create them server side as part of the request) but I don't know their ID.

And I want to insert the single item into the view, not a collection. Of course there are workarounds, but just not so convenient.

[wycats]

Makes sense.

[wagenet]

For now, you can use jQuery.ajax to hit the endpoint and then load into your store.

[wagenet]

You can also use a fake id, such as 'singleton' and have you adapter handle this case. Judging by #58 this is not something we have explicit plans to support, though a PR to hide the 'singleton' id might be acceptable.

[lukaiser]

What's the status of this request? I don't really get it. I'm absolutely in favor of it. In my case, I have a find query App.MyModel.find({q: "test"}) witch always returns only one model (not always the same). Currently I have to use the same workaround as described in Issue #385. A fake ID isn't working, because it's a query. And using jQuery.ajax is in my opinion totally the wrong approach, because it's a parallel structure and I can't just switch my adapter, if I want to.

[darthdeus]

This is also related to #551

[pdf]

So, wait, @wycats said this makes sense, and this and related issues (#58 #97 #385 #393 #551 possibly others) keep coming up, yet this seems to get rejected out of hand... is there some way to find consensus?

[jdivock]

Chiming in that I find this to be an odd oversight. I just spent a good deal of time trying to hack up a way to load a simple currentUserProfile . . . which is just that, the profile of the current user. It has no idea, just a series of value related to the user returned from the middle layer.

Backbone and other frameworks allow for an singular instance that is just a model and not a collection, I find it odd that this feature keeps getting deferred.

[wagenet]

See #551.