Chris Krycho

Results 144 issues of Chris Krycho

- [x] pull in [these posts/answers to questions](https://discuss.emberjs.com/t/glimmer-component-args-typescript/17155/5) and polish them up - [ ] explain why doing this doesn't work: ```ts class MyThing extends Component { args!: { something:...

docs

We [currently document][current] one gotcha for addon authors *building* addons in TypeScript: > Because addons have no control over how files in `app/` are transpiled, **you cannot have `.ts` files...

docs

> Why do we need `allowJs`? I've had issues with TS errors being ignored until publish time (and breaking publishing automation) because `allowJs` is explicitly set to `false` by `ts:precompile`...

question

### Which package(s) does this enhancement pertain to? - [x] @types/ember__engine ### Please write a user story for this feature Follow the form As a consumer of Ember's types, I...

types:core

When setting up a brand new ember-cli-typescript installation, there are a number of ESLint errors right out of the gate, including parse errors for things like module declaration for merging...

enhancement
question
docs

We get regular questions about how to deal with not having allowed values on the `this` of the `TestContext` (e.g. [here]). We should document an example of how to set...

docs

I get semi-regular questions—and more so as Ember Data is using ember-cli-typescript—why ember-cli-typescript is in `dependencies` instead of `devDependencies`. Explaining why this is the case, and when/under what conditions it...

docs

The existing docs are very rough in structure: basically we just split out what we had in the 1.x README when we did the 2.x release. This was better than...

docs

### Which package(s) does this enhancement pertain to? - [x] Other: [@ember/ordered-set](https://github.com/emberjs/ember-ordered-set) ### Please write a user story for this feature Follow the form > *As a **user or developer...

types:core

We need to make it so our builds are not *failed* by running against ember-cli beta (or typescript@next), even if we want to *know* that they're failing on beta.

build
ci