Yeah I should, you're right. I'm working through a huge to-do list on that and CoffeeComplexity right now, but I'll add that on the pile too. :)
There is no storage on the back-end, it just calls a little node library that I wrote and spits out the result.
The work to target other languages is underway, I've split out the AST walking to a separate repo, so it just requires writing a walker implementation for the target parser and you're done. The CoffeeScriptRedux walker is currently in development, with LiveScript planned for after that.
So I met a guy recently who is building something similar to the ComplexityBot idea you describe. It's called sidekick and looks pretty awesome from my initial play around with it.
There is no storage on the back-end, it just calls a little node library that I wrote and spits out the result.
The work to target other languages is underway, I've split out the AST walking to a separate repo, so it just requires writing a walker implementation for the target parser and you're done. The CoffeeScriptRedux walker is currently in development, with LiveScript planned for after that.
So I met a guy recently who is building something similar to the ComplexityBot idea you describe. It's called sidekick and looks pretty awesome from my initial play around with it.
* https://www.sidekickjs.com/