-
On my first Ember Data project using an ActiveModel API I started developing with the default serializer and adapter since I was not aware that I had to change them. This worked fine for a while, but…
-
When a computed property on a 1-to-1 relationship references the other part of the relationship, and it has just been loaded into the store (or is in the process of being loaded, after say a POST), an…
-
After rollback() is called on an already saved model, belongsTo and hasMany relations become null in the model. This change is temporary, it is not persisted in the store, the relations are loaded cor…
-
I've had to add a custom `save` method on models that have asyc relationships as the JSON sent up to the server clobbers the list of related ids.
For example, the code below gets all the related obje…
-
When generating the occurs information on the website, we display this as part of the description of an element.
We should do this better.
One suggestion is to add it to the 'Rules' section
-
Descriptions are different:
Website:
> The contact mailing address.This element may occur any number of times.
Spreadsheet:
> The contact mailing address.
ghost updated
9 years ago
-
ie. update the XML so that instead of repeated elements with the xml:lang attribute we have narrative subelements.
-
As described on this stack overflow:
http://stackoverflow.com/questions/19816871/how-to-fork-a-model-in-ember-data
There's a use case which keeps popping up in various forms that doesn't seem to be a…
-
When a model defines an asynchronous relationship, the async relationship are fetched during the serialization process before a save even in cases where the models are already loaded into the store.
…
-
In attempting to work around #4681 at @mmun's suggestion I ended up with something like this, expecting two invocations of `addItem` for each item (one empty object before setupData was called and onc…