Closed chenglou closed 11 years ago
I am about to begin evaluating your node port of Huxley vs the python original. One of the reasons is, we have use Grunt for our build process. Having grunt be aware of Huxley would be nice.
Having said that, I am not terribly familiar with Grunt, myself (not yet anyway), so I don't know if its necessary either.
It really shouldn't be hard, either you call the command line method or you call one of the three methods exposed in bin/hux
. I'm worried about grunt-Huxley making task running a bother though, since it takes long to finish so you either put it at the end or as a separate task (which actually takes more typing. But you get the advantage of having a local dependency only).
The local dependency is a plus. And I am not sure what your background is, but I am a recent migrant from the rails world, and I saw test suites that could take 2 hours. So I am not so concerned with a bit longer compared to js test suites...
It's not a question of what the old tools do; Huxley is an entirely new paradigm and I won't cushion on the old constraints if they don't give a good experience. Local dependency is indeed a very good reason to add grunt support. I'll do it.
@igreulich relevant: any thought about #13?
@igreulich thanks for the input on #13. Work has started on grunt-huxley; I'll release it as soon as it's ready and it really shouldn't take too long.
Btw, how's huxley working so far?
@chenglou No problem on #13.
Huxley is working great! (Now that I have a firm grasp of how it is supposed to work.)
Right now we are just using it locally, but we will be moving it to a CI server eventually.
Fresh out of the oven! https://github.com/chenglou/grunt-huxley
Not sure if this is even necessary.