You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2018. It is now read-only.
Off topic a bit, but I'm curious how you were thinking of handling "Generate TS files for app files".
We're looking to build an internal generator and provide TypeScript as an option, but I don't really want to have to maintain both a .js and a .ts version of each file.
The least bad option I can think I was considering having the "canonical" files be written in TypeScript, and then if the user chooses to use JS code, we'd run the sources through tsc with target: es2015, and emit those files.
But, I haven't seen this in any other generators, so I'm interested in what your thoughts were. Cheers!
I haven't really thought much about it at all, really. I don't use TypeScript at all, but it's something I'd like to support here since we have the definitions and @Hotell is so passionate about it ;)
I think your idea of making the TS files the "canonical" ones and then transpiring away anything not in JS when generating the JS versions would be interesting.
However, since the Skate source is going to be in Flow, it might make more sense to do that with Flow instead (having the types in there by default and optionally removing them when generating a new component).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
index.js
Useful links
The text was updated successfully, but these errors were encountered: