ember-jsonapi-resources icon indicating copy to clipboard operation
ember-jsonapi-resources copied to clipboard

Lightweight persistence for an Ember CLI app following the JSON API 1.0 spec

Results 8 ember-jsonapi-resources issues
Sort by recently updated
recently updated
newest added

I used this for about a couple years at my old job. I personally don't have any production app using this (other then my personal blog website). Maintenance needs: -...

`ObjectProxy`s for `toOne` relationships were initialised with a fresh `Ember.Object.create()` as their content. Because of this, you can not do this: `if (resource.get('some-to-one-relationship')) { ... }` or `{{#if resource.some-to-one-relationship}} ......

This is somewhat related to https://github.com/pixelhandler/ember-jsonapi-resources/pull/141. related proxy's are promise/able, except when they're not. Empty relationships do not support promises, so you can't always go `model.get('some-relationship').then(relationship => { if (relationship)...

http://jsonapi.org/format/#crud-updating-responses-204 204 no content is a valid response, but it does not trigger any update on the `Resource` that was updated (since `deserialize` has nothing to do).

These are my WIP changes regarding relationship tracking. This is: - [live attr and rel tracking](https://github.com/pixelhandler/ember-jsonapi-resources/pull/140) - [handling 204 responses, dealing with ember-fetchjax change](https://github.com/pixelhandler/ember-fetchjax/pull/1) - seperate `addRelationship` and `_addRelationship`, the...

I think we need better tests. Some that test the entire chain of adapters, mixins, models, etc. The current unit tests are very fragile and rarely test actual use-cases (with...

`_changedAttributes` and `_changedRelationships` are Observable arrays, to allow live dirty tracking.

Looks like ember-beta is failing due to potential changes and deprecations with _lookupFactory