Chris Krycho

Thanks for reporting. FWIW, the problem here is the same as the problem with `Transition` (and which *technically* should exist for `RouterService` as well, but we don't have alignment in...

Thanks, @hmajoros! The fundamental issue here is that we don’t currently wire up the compiler API to use the `build` API equivalent—only to use the older `watch` mode equivalent, which...

As noted on #1272, there is a general need for workspace support, of which this is a part. I will be building out a plan to tackle that and will...

Thanks for opening this! @jamescdavis I believe you know Ember Data best of the current maintainers (and cc. also @runspired) – the docs [say][query] we ought to return a `Promise`...

Thank you for reporting this! This *appears* (at very first blush and without having investigated at all) to be a case where TS 3.7 is actually being more strictly correct....

What was the actual code that caused this? I assume it wasn’t a local declaration of a `ComoutedProperty`? 😂

Hadn’t been any motion, but is likely to be a lot of motion in related spaces starting in about two weeks: we’ve kicked off a “strike team” with the aim...

In general, the workaround is: switch to native classes and use native getters and setters. The problem just goes away if you are not using classic classes with TypeScript. The...

Thanks for the report! This makes sense; Ember Data has made a lot of progress and the types have changed a lot over the 3.x series (in ways which are...

Thanks for opening this! For anyone else watching this issue: the types on DT match the docs, but the actual implementation totally supports (and has types to support!) using `document`,...