Allow store.find to accept query-params with id (Closes #1576).

[abuiles]

This is a first stab at supporting extra query params when requesting an specific id.

[abuiles]

I'm thinking about how to handle model.reload(), shall we "remember" the params used for finding a record, or just allow reload to accept a query params. I'm more inclined towards accepting queryParams in the reload, it might not be responsibility of the record to know that.

[bradleypriest]

This feels like quite an edge-case to me. I'd like to see a better use case than {include: "comments"} before we add this. Maybe put it up on the discussion forum first.
Cheers

[abuiles]

@bradleypriest This is related with #1576 please check the comments there, this has been adopted
recently in jsonapi, which I think we are taking as reference. Actually @wycats was the one accepting the change in jsonapi
json-api/json-api#145

[abuiles]

This could also help resolve #51

[abuiles]

@bradleypriest http://discuss.emberjs.com/t/ability-to-use-query-string-params-with-store-find/3619

[abuiles]

@wycats could you please have a look at this? Would make more sense to have this just in the JSONAPI adapter?

[abuiles]

@igorT ping

[igorT]

I think the reload case is a bit tricky. In the json api spec, query params are used for requesting sideloading. In my mind a reload is tied to a specific record that you are reloading. If you are doing a reload and you pass in {include:comments} should the comments also go into a reloading state?

[igorT]

@wycats thoughts?

[wycats]

As @igorT points out, this doesn't work for all cases. I'd like to think about this more; at present, it feels too much like a scenario-solve than a comprehensive solution.

[stefanpenner]

we should likely enumerate the scenarios this must work for, this will likely guide the correct solution.

[adamlc]

Any updates on this? :)

[kodayashi]

Hi @abuiles, was this merged? The third parameter seems to be ignored in the latest release.

[abuiles]

@kodayashi no, it wasn't merged.

[kodayashi]

Gotcha, thanks for the update @abuiles. I believe @stefanpenner is looking for use cases here. Currently, I'm looking to use query parameters for a given 'model' object opposed to an entire collection of model objects:

(theoretical) -- store.find('model', 1, {filter: 'filter_value'}) -- Only one model object needs to be loaded. Query param is then applied against object.

(today) -- store.find('model', {id: 1, filter: 'filter_value'}) -- Entire model collection is loaded, then one model is filtered, then query param applied.

For our use case, the param defines a filter for a Graph object that's associated with the 'model' object. Hope that helps.