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
I thought it might be helpful as documentation to try adding type annotations to the code base. I guess I forgot that the annotations would have to be stripped out before runtime. That sucks, because it's nice that the CLI code doesn't have any build process right now. Stripping the types would require a build step, and separate source/build directories. Or runtime overhead by stripping them dynamically.
It feels like 'useless overhead' at the moment, but if you can do a build process then that's cool too. However, I think writing typescript definitions (tsd) for the projects generated by the CLI for the Espruino runtime is probably a better use of time surrounding types.
I thought it might be helpful as documentation to try adding type annotations to the code base. I guess I forgot that the annotations would have to be stripped out before runtime. That sucks, because it's nice that the CLI code doesn't have any build process right now. Stripping the types would require a build step, and separate source/build directories. Or runtime overhead by stripping them dynamically.
A branch with some basic annotations is here: https://github.com/joefraley/thingssdk-cli/tree/feature/flow-types
@chalkers does it seem worth while to bother with a transpile thing, or does it seem more like useless overhead?
The text was updated successfully, but these errors were encountered: