Thomas Gossmann

@rwjblue I do understand this dilemma... and thought about it. My first thought was providing two "exports", one wrapped in babel, the other not... but that would also be stupid....

I added some tests. I copied over all the relevant types from `(element)` helper as well as a component receiving it. Feels a lot, but makes it accurate. If this...

Looks like the first step. In the long run, I think this addon here will become obsolete and everything is moving to `@storybook/ember` - but we may keep integrations as...

CI is against your NPE fix o_O ?!? Can you take a look. I'd have merged it if it went green.

@eirslett Thanks for working on that. Will be off on vacation soon. So earliest will get back to it mid/end august. I'm super keen to get this running, so defo...

Any idea to "merge" in `@arg` from [sparkles-decorators](https://github.com/gossi/sparkles-decorators) to provide defaults _and_ being type-checked? Since arguments don't have a default, which was the idea for `@arg`. It's not good to...

I see your point, makes sense. Having `@arg` and `@argument` is weird. But your semantics of `@readsWithDefault()` kinda imply (at least to me) that the default is given as parameter...

Oh, renaming `ts` files that re-export `gts` files to `gts`, aka `index.ts` -> `index.gts`. Then I run into very unreliable errors: Renaming this from `ts` to `gts`... is only a...