Chris Thoburn
Chris Thoburn
In many situations we don't need to flush remote updates until access has occurred. This improves performance when the received state would not be readily observed by the consuming application,...
When a record declares the same type + inverse field repeatedly error messages can be misleading because the relationship becomes misconfigured: ```ts export default class Nest extends Model { @hasMany('modaction',...
- [ ] split checks across multiple machines to speed them up - [ ] stream check updates to the comment - [ ] find a way to make each...
Collections are a great primitive for many ad-hoc relationships. Collections are often capable of being patched on the client to reflect an operation being performed remotely. We should make it...
Similar to https://github.com/emberjs/data/issues/8855 but for response handling Processing results has non-trivial baseline overhead, especially for relationships. Often requests made close to each other contain result payloads that require work that...
Currently, requests triggered around the same time (for instance by multiple components or routes) will resolve as soon as their data is received and process. This can lead to a...
This is a bonus feature :) consider it *highly* experimental at the moment. we plan to ship a stable version of this sometime in 5.x
As emberjs/rfcs#487 lands and with the deprecation of `Model.toJSON()` in emberjs/rfcs#522 we should investigate improved primitives and APIs for the Ember Inspector.
I've been noticing this on most test-runs for EmberData recently. ``` tests/main test:try-one: ERROR Summary: tests/main test:try-one: - broccoliBuilderErrorStack: [undefined] tests/main test:try-one: - code: EADDRINUSE tests/main test:try-one: - codeFrame: [undefined]...
Currently, ember-cli will error if "name" in package.json does not match the name in `index.js`, for instance: ``` ember-cli: Your names in package.json and index.js should match. The addon in...