Although most of our collaboration takes place on Github, IRC
(#emberjs on freenode.net), and our Discourse site
the Ember Data team meets privately every
Wednesday at 11am PST through Google Hangout for a weekly
discussion of all things Ember-Data.
Attendees
https://twitter.com/ebryn),
[@krisselden](https://twitter.com/krisselden),
[@machty](https://twitter.com/machty),
[@rwjblue](https://twitter.com/rwjblue),
[@trek](https://twitter.com/trek),
[@stefanpenner](https://twitter.com/stefanpenner),
[@wagenet](https://twitter.com/wagenet),
[@tomdale](https://twitter.com/tomdale),
[@wifelette](https://twitter.com/wifelette),
[@wycats](https://twitter.com/wycats)
[@hjdivad](https://twitter.com/hjdivad)
[@terzicigor](https://twitter.com/terzicigor) -->
@tomdale,
@wycats,
@terzicigor
PushPayload discussion
We discussed the PushPayload proposal
@wycats concluded that the original decision for pushPayload on the store to accept a type argument was a mistake.
Decided that instead of creating several new hooks, the best course of actions seems to be to add a normalize method to the store.
Thus instead of doing pushAndNormalize from the discuss proposal, one can do
store.push(type, store.normalize(type, payload))
It also seems nice to have a normalize method on the store as the inverse of serialize which already exists on the model.
Group Coalescing
@hjdivad and @terzicigor recently added a
groupedRecordsForFindMany hook on the findCoalescing
branch to enable users to decide how to group coalesced requests.
The hook was given a +1. We also realized that this hook will also solve the problem of URLs being too long for findMany