J.Olufsen
J.Olufsen

Reputation: 13915

How to design API so it would fit REST conventions and Ember.js way?

Would be a good practice to merge all properties of Item:

{id: 1, priceId:1, property1:0} with its corresponding Price {id:1,seasonalPrice:123,regularPrice:120} into:

{id:1,property1:0, price:{seasonalPrice:123,regularPrice:120}}.

Ember most likely can handle linking and combining(merging) two jsons that arrive as two promises from backend REST API into one model. What is the best approach to desing API and consume using Ember?

Upvotes: 2

Views: 99

Answers (1)

ykaragol
ykaragol

Reputation: 6221

For Rest API designing, you can read:

You can apply Richardson Maturity Model level 2 or 3 with Ember Data.

With Ember, you can use any level that is suitable for your case. In our case we prefer to stay in level 1 with a strong backend (written in Java) and not to use Ember Data.

Upvotes: 2

Related Questions