Add more tools

[fkling]

There are many more tools besides jscodeshift which could be added to the ast explorer for quick prototyping / testing. For example:

• eslint plugin development
• babel plugin development

To make adding new tools easy, some refactoring of the client side code and the DB schema is necessary. I already have a proof of concept commit locally but it still needs more tweaking.

The current idea/plan is that "tools" are React components which are rendered below the code editor and ast panel (just like the transform tool now) and which have access to

• The current parser
• The current code
• An API to highlight parts and show errors in the code editor

Tools would also be able to specify which parsers they work together with. They could render whatever interface they need.

[hzoo]

👍 been using this for jscs and babel-eslint. Can be a lot of work to debug/make rules/tests. Awesome stuff @fkling!

[jasonLaster]

👍

[fkling]

First step is done: The logic is more split up to allow custom transformers (but not custom views yet).

[jasonLaster]

nice! can't wait to see that

[fkling]

@jasonLaster: If you go to http://astexplorer.net/, you can now select between "jscodeshift" and "babel".

[fkling]

We have support for PostCSS now.

[fkling]

I'm closing this for now, since we have everything that I originally wanted. In the future, we might also want to give more liberty to tools and let them render whatever they want in their panel (i.e. they wouldn't be restricted to just two text input fields).