Custom endpoint URLs for specific filter/action

My endpoints are:

/articles # all articles
/users/:id/articles # all articles by user

I want to use the same defined resource for both endpoints, but with a different filter. I see that endpoints can’t be changed after definition, even when sending a new one as an option.

Article.findAll() // /articles
Article.findAll({}, { endpoint: "/users/" + userId + "/articles" }) // /users/:id/articles

How about adding to DSHttpAdapterProvider http methods overriding option, exactly like options.baseUrl || resourceConfig.baseUrl but for endpoint?

DSUtils.makePath(
  options.baseUrl || resourceConfig.baseUrl, // exists
  options.endpoint || resourceConfig.endpoint // currently only resourceConfig.endpoint
)

[simpixelated]

Thanks for the quick response! I think I’m actually looking to use the relations functionality. For example, my API endpoint is ‘posts/:postId/comments’. I’m probably doing something wrong, but it seems like using the DS.find() method requires an ID for the comment. Unfortunately the API returns a 404 if that extra parameter is defined (‘posts/1/comments/1’ returns 404).

http://plnkr.co/edit/If17RKyeUaGZIssb9KeG?p=preview

EDIT: I used the same relations structure from issue #162 and was able to solve my problem… sort of. On first load I get the warning “DS.findAll(mls, params[, options]): response is expected to be an array!”. But the next time I call loadRelations it gets the data from the cache.

[altschuler]

How is this done in v3?

Edit: FWIW this is what I was looking for: http://www.js-data.io/v3.0/docs/js-data-http#http-actions