Kevin Pfefferle

@alexraputa We're not doing that exactly, but the constructor in the "offending" Component does use `createRecord` to initialize a new data model that is internal to the Component. Something like...

@runspired Ours is not a `createRecord` with `peekAll`, but it is a `createRecord` that is associating the new model with an existing model that has been passed into the component...

@runspired I can understand how a component associating a new record with an existing one could reasonably be understood as mutating the related component in a way that invalidates it...

@runspired We literally only have one component in our application that's doing this, so I'll give those approaches a shot to get us back on the latest stable train 👍

@rreckonerr Are you using `setupEmberTableForTest()` before each test? It configures the test waiter necessary to make this work. See the README: https://github.com/Addepar/ember-table#writing-tests-for-ember-table-in-your-application

Both https://github.com/ember-cli/ember-new-output and https://github.com/ember-cli/ember-addon-output still have 4.8.0-beta.0 as their latest release. These repos are linked to from the release notes, but the links haven't worked for 4.8 stable and 4.9...

@bakerac4 Trust me when I say there's support for this inside of Addepar as well. In fact, I may have something for us to look at sooner than you might...

@bakerac4 I'm quickly settling on an approach I'm pretty happy with for the app I work on at Addepar. Once I review it with my own team to get some...

I just opened a PR to add the Glint types I've been using internally as a public experiment: - https://github.com/Addepar/ember-table/pull/968

Addon-provided Glint template types have been released in version [5.0.1](https://github.com/Addepar/ember-table/tree/v5.0.1). They are considered experimental, may change at any time, and not subject to our semver commitment. Right now these types...