Ember Data Conference Minutes-2014/06/25


Although most of our collaboration is conducted on Github, IRC (#emberjs On freenode.net), and our Discourse site
The Ember Data team meets privately via Google Hangout every Wednesday at 11 am Pacific Standard Time to discuss everything about Ember-Data every week.

participant

@tomdale,
@wycats,
@terzicigor

Serializer refactoring

We discussed how to best refactor the existing serialization program, especially by @BMac Decompose Rest Serializer into JSON Serializer + Sideloading mixin. In the process of dealing with it, several questions were raised, including how to ensure that the mixins that extend the JSON serializer (now an embedded record mixin, and a Sideloading mixin in the future) call their hooks in the correct order, and how they do not Will interfere with each other.

Deciding to refactor as a mixin is a good idea. Tom proposed the idea of ​​establishing a serialization pipeline, but we decided to put it aside for now. Decide to wait for more use cases before deciding whether/and how to reorganize the hooks so that the mixin is easier to use/write.

Zalgo Promise Agency

Discussed how to solve the problem of serialized asynchronous relationship.
@terzicigor with @stefanpenner The idea of ​​having a Zalgo proxy has been proposed before, the proxy will be passed to the serialization hook, and the proxy’s access to the relationship as a synchronization.

It was decided that this is a good idea, but it needs to be fully specified and a better name is needed.

Synchronous settings for asynchronous relationships

Discussed how to set up/bind two asynchronous relations. For example, currently binding asynchronous belongsTo to asynchronous hasMany does not work because the binding tries to set promiseProxy instead of the model.

Decided to let template binding work with promises, while not allowing users to manually set promises.Need some Ember-Metal work to start working

Explore a good way to get a synchronized version of the model

Decided to explore a good way to call then a model and/or multiple relationships, which will return a promise, and once all the relationships are loaded, the promise will be resolved.

Thinking about how to merge asynchronous waits from ES7

@wycats I am glad that Ember-Data supports the possibility of asynchronous wait from ES7. Say it can better handle asynchrony. There is no conclusion because there is no time for people to investigate.



Leave a Reply

Your email address will not be published. Required fields are marked *