leddgroup / typescript-transform-macros Goto Github PK

I recently learn haxe and macros is a powerful tool, Let me give you a couple of thoughts:

• I would expect macros to be a preprocessor TypeScript-> TypeScript transformation. (currently they seem to be implemented as transformer TS->JS
• I know tsc currently doesn't allow to register a transformer as plugin . (so it's better to just build a preprocessor TS->TS tool - doesn't need to be a plugin)
• Also, as in haxe, TypeScript AST own API types can be used by the user to reference / select / build code. There are nice libraries for select nodes / manipulate the AST and concretely declare code programmatically (check the tool at the bottom/left of this tool https://ts-ast-viewer.com/). On the other side, this could limit things you can do, for example, adding a new method - how the type checking would work in that case... (just thinking aloud- )
• I personally would not install ttypescript or anything different than the official thing for generating js... Is it really worthwhile even in the case that the output is js ? isn't make more sense to have an intermediary TS->TS tool instead ?

In summary I think this is an awesome idea, feel free to close this / I would be glad to keep discussing on this. thanks!

From the example in readme, it seems the expanded code is going to be executed in the runtime, instead of in the compile time. If this is the case, it seems similar to just inclining the function (with name conflict avoidance)

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.