hubot ^3.0.0 and hubot-test-helper in JS ES2015

[cirpo]

Hi, I'm in the process of writing hubot-test-helper in JavaScript instead of CoffeeScript and support the new Hubot 3.0.0 release which is entirely re-written in JavaScript (ES2015).

Before opening a new repo/npm package I would like to know if you're already working on a pure JavaScript version for this (awesome) helper in order to avoid wasting time and help you with it.

Let me know, thanks

[mtsmfm]

@cirpo Hi, thank you for letting me know!
I just start re-writing, however, it may take a while.

It's also welcome to send another PR to re-write when you've done all of TODOs written in the description of the PR! (#49 (comment))

[cirpo]

@mtsmfm shall I send PR on the es2015 branch? How do you want to manage it?

[cirpo]

and, what do you think about using jest instead of mocha?

[mtsmfm]

shall I send PR on the es2015 branch? How do you want to manage it?

Sending PR on the es2015 branch is preferable.
Hopefully, I'll finish this task by next weekend so please be patient if you can wait a while.

Normally I can't work a lot on this repo on a weekday so creating completely another one is also ok if your branch has completed the TODOs.

[mtsmfm]

and, what do you think about using jest instead of mocha?

It sounds interesting but please don't mix with this issue 🙏

I only know the name "jest" and haven't tried yet so I'm very happy if you create another issue and tell me pros-cons on the created issue.

[cirpo]

@mtsmfm sure, in my opinion, we could use this issue for discussions around porting this awesome lib in this issue. I would avoid having several discussion all over the place, what do you think?
For example hubot documented and discussed everything in this issue: hubotio/evolution#4

[cirpo]

I will wait for the next weekend, otherwise we will both do the same thing at the same time.

[mtsmfm]

in my opinion, we could use this issue for discussions around porting this awesome lib in this issue. I would avoid having several discussion all over the place, what do you think?

If a topic should be done with the porting (eg. changing usage), of course it should be discussed in this issue.

But using jest instead of mocha can be done without porting, so I asked you to create another issue 🙏

[cirpo]

Will do then, thanks 🙌

On Sun, 1 Oct 2017 at 9:48 am, Fumiaki MATSUSHIMA ***@***.***> wrote: in my opinion, we could use this issue for discussions around porting this awesome lib in this issue. I would avoid having several discussion all over the place, what do you think? If a topic should be done with the porting (eg. usage), of course it should be discussed in this issue. But using jest instead of mocha can be done without porting, so I asked you to create another issue 🙏 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#47 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADINKUIwqzK9rhZO_bj1iA8sSQF2DpGks5sn1HPgaJpZM4PiCVJ> .

-- @cirpo mobile: +44 7492 014 290 skype: cirpolo linkedin: http://linkedin.com/in/cinellialessandro github: http://github.com/cirpo

[mtsmfm]

@cirpo I've just finished and released!

[cirpo]

@mtsmfm congrats, I'll have a look and send PRs if needed, thanks