RFC: non-crud operations: Is ember-ajax working for us?

[pnw]

Questions:

Is ember-ajax working for us?

Current ember-ajax paradigm:

• ember ajax + putting actions on models
• handling forms in the client that don't have an ember model to work on
• manual error handling when you don't have a model

[anotheredward]

On the loopback side, I've started to tend towards hitting a CRUD endpoint with a query parameter rather than remote methods. Otherwise you end up re-implementing a whole bunch of stuff that is out of the box with CRUD methods.

[pnw]

On the loopback side, I've started to tend towards hitting a CRUD endpoint with a query parameter rather than remote methods. Otherwise you end up re-implementing a whole bunch of stuff that is out of the box with CRUD methods.

I don't understand. @anotheredward for some context, this mostly addresses RPC's, the inputs for which either have no corresponding data model or act on an existing record, requiring no additional inputs.

[anotheredward]

I have misunderstood this PR :)

[anotheredward]

Did we make any headway on this issue @pnw ?

[pnw]

I don't think so, but I've been pretty happy with ember-concurrency.

[anotheredward]

Is that pretty much covered by: https://www.mediasuite.co.nz/blog/day-life-ember-concurrency-task/ @pnw ? Or is that something that deserves another blog article?

[pnw]

Well that's a totally different topic really. That blog post is about ember-concurrency, and this issue is about ember-ajax 😛

[anotheredward]

Seems good, also consider: https://github.com/ember-cli/ember-fetch This can be covered in the "Commonly use Ember Plugins" blog article.