Option Test Patch #27
Conversation
|
cc @tkellen |
|
@tkellen did this resolve the issues you were having with options? |
|
yup. everything looks good now--thanks for all the great work! tomorrow, i'll get this test suite running on travis.ci |
|
@tkellen neat, haven't messed with Travis but its nice to have auto testing. Oh and I will do one more pass over zip after rebasing, hopefully it doesn't blow up on me again! should be def be good for tomorrow then maybe cut a release? |
|
sounds like a plan! |
|
@tkellen have you considered using tags now that things are taking off? I think it would be a nice touch to compare between releases and such. |
|
yup! i'll start using tags once we get to 0.1.0 |
|
whats the goal between now and then? i know this is like an addon pack for grunt but maybe we should start wiki and get roadmap going, I am willing to dedicate some time each month towards it. |
|
grunt 0.4.0 needs to drop, and I want completed docs for all the tasks (and a listing of tasks & links to said docs in the main README). I also want to talk with errcw about changing the jade task from src / dest keys to dest: ['src','src'...] for consistency with all the other tasks. If you have the time/inclinaton to tackle any of that, I'd greatly appreciate it. |
|
@tkellen I can prob help out with the jade task if errcw is busy or such. shouldn't be too bad as i've wrote three tasks in the "new" style. README would be good, what do you want to do for docs, like parameter listings or links to related library? |
This should fix the option test bug introduced by #25. It boils down to you have to completely reload the tasks within nodeunit tests. For some reason,
npm testisn't effected butgrunt testis, maybe due to scope?