json-api

I have a fairly specific problem that I was hoping one of you really intelligent folk might know a solution for (or even a workaround at this stage) Specifically, I'm dealing with action cables, nested JSON, and the JSONAPI . I have an asset model, which has some attributes like name , desc etc. but it also has an attribute called state which is a complex nested JSON object. // app/models/asset.js export default DS.Model.extend({ // Attributes name: DS.attr('string'), desc: DS.attr('string'), state: DS.attr(), lastSeen: DS.attr('date'), }); When anything on the asset changes in the backend, it

Ignoring 3xx responses for a moment, I wonder why the HTTP location header is only used in conjunction with POST requests/201 (Created) responses. From the RFC 2616 spec : For 201 (Created) responses, the Location is that of the new resource which was created by the request. This is a widely supported behavior, but why shouldn't it be used with other HTTP methods? Take the JSON API spec as an example: It defines a self referencing link for the current resource inside the JSON payload ( not uncommon for RESTful APIs ). This link is included in every payload. The spec says that you MUST include

i have a json data from my server: { "post": { "id": 1, "title": "Progressive Enhancement is Dead", "comments": ["1", "2"], "links": { "user": "/people/tomdale" } }, "meta": { "total": 100 } } look exactly like the documentation ( https://guides.emberjs.com/v2.5.0/models/handling-metadata/ ) i try to get the meta object with no success export default Ember.Route.extend({ model() { var data = this.store.findAll('post'); data.then((result) => { let meta = result.get('meta'); console.log(meta); //this return me undefined }) return data; } }); You are using findAll method and it does not support

I have been tearing my hair trying to make the test to pass. I have a JSON API that looks like this: { "data": [ { "id": "b99f8173-0492-457f-9de9-6c1d8d6832ed", "type": "manufacturer_organizations", "attributes": { "account_number": "random test 123" }, "relationships": { "organization": { "data": { "id": "fb20ddc9-a3ee-47c3-bdd2-f710541ff89c", "type": "organizations" } }, "manufacturer": { "data": { "id": "1", "type": "manufacturers" } } } },... I am trying to make a post :create test in rails. let!(:manufacturer_organization) {FactoryGirl.create(:manufacturer_organization)} let(:manufacturer

I am using Ember 1.13.7 and Ember Data 1.13.8, which by default use the JSON-API standard to format the payloads sent to and received from the API. I would like to use Ember Data's built-in error handling in order to display red "error" form fields to the user. I have formatted my API error responses as per the JSON-API standard, e.g. {"errors":[ { "title":"The included.1.attributes.street name field is required.", "code":"API_ERR", "status":"400", } ]} and when I attempt to save my model the error callback is being correctly executed. If I look within the Ember Inspector I can see that the