Ship replacement typed blueprint files for core blueprints

[seawatts]

No description provided.

[davewasmer]

I don't think we need to actually override any blueprints, just expand what we are currently doing on post install to make sure we:

1. Convert dummy app files to .ts
2. Add a tsconfig.json to dummy app
3. Add denali-typescript to dummy app package

[seawatts]

I guess what I meant is when we do denali generate migration foo-bar it still produces a .js file and then I have to go manually convert it.

[davewasmer]

Ah. To fix that, denali-typescript would need to ship with all the blueprints Denali core does. That's certainly doable, and unfortunately I don't see a more efficient way of doing it.

We also need to think through precedence here. If both denali and denali-typescript ship with an action blueprint, for example, and I type denali g action, which should run? Right now you can always prefix the addon name to be explicit, i.e. denali g denali-typescript:action, but I'm wondering what the default behavior should be (not sure what it is right now).

[seawatts]

Hmm, good point. What if denali cli had some sort of events that fire through the lifecycle of calling a blueprint that typescript could hook into?
i.e.

afterBlueprint()?
Then in there denali-typescript could just go through and run .js -> .ts on all the files again.

[davewasmer]

That might work for some use cases, but I think the ideal solution for denali-typescript users would be if the generated blueprints weren't just JS files with the TS extension, but were actually typed Typescript code.

Another way to think of this: how would denali-coffeescript work, since unlike Typescript, regular JS isn't valid Coffeescript?

[seawatts]

Ah good point.

…

On Mon, Aug 28, 2017, 11:41 Dave Wasmer ***@***.***> wrote: That might work for some use cases, but I think the ideal solution for denali-typescript users would be if the generated blueprints weren't just JS files with the TS extension, but were actually *typed* Typescript code. Another way to think of this: how would denali-coffeescript work, since unlike Typescript, regular JS isn't valid Coffeescript? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACDIwqeBrlmTBI6loqIJxYp5tcaX637dks5scwnqgaJpZM4PAUDS> .