Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CoffeeScript -> JS #13

Merged
merged 3 commits into from
Jan 9, 2018
Merged

CoffeeScript -> JS #13

merged 3 commits into from
Jan 9, 2018

Conversation

TimvdLippe
Copy link
Contributor

This PR updates all coffeescript files to JS ES6 to be compatible with Hubot 3.

Fixes #12

@stephenyeargin
Copy link
Member

@TimvdLippe If you have a moment, tell me a bit more about the Hubot v3 requirements (namely, where I can keep up with them). I maintain several packages and am curious how much work is ahead. 😬

@@ -14,7 +14,7 @@
},
"dependencies": {},
"peerDependencies": {
"hubot": "2.x"
"hubot": "3.x"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this make it no longer viable for v2 Hubots?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that is correct.

index.js Outdated
* DS205: Consider reworking code to avoid use of IIFEs
* DS207: Consider shorter variations of null checks
* Full docs: https://github.com/decaffeinate/decaffeinate/blob/master/docs/suggestions.md
*/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can probably delete this block. As an aside, the new hubot:script generator probably has a better version of this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup did this locally but forgot to do it here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done 👍

@TimvdLippe
Copy link
Contributor Author

@stephenyeargin Basically as far as I can understand, Hubot 3 is the same as Hubot 2, but all the coffeescript related stuff is removed. With these changes, I was able to make it run again. The other breaking changes are described at https://github.com/hubotio/hubot/releases/tag/v3.0.0

@stephenyeargin
Copy link
Member

Basically as far as I can understand, Hubot 3 is the same as Hubot 2, but all the coffeescript related stuff is removed.

Yeah, I noticed that in core. Wasn't sure what the plan was for the community packages if they had to move to ES6 or if they were fine as-is. The peerDependency change probably made the bigger difference for your core issue, but I'm wondering if there's a notation we can use to indicate either 2.x or 3.x.

@hubot-scripts/hubot-youtube If you have a moment to weigh in on Hubot^Next as it relates to packages, that would be enlightening. ✨

@TimvdLippe
Copy link
Contributor Author

but I'm wondering if there's a notation we can use to indicate either 2.x or 3.x.

There certainly is, but sadly Hubot 3 is incapable of consuming a package with just coffeescript files. This forces the package to convert to JS instead 😢

@stephenyeargin
Copy link
Member

Weird. I feel like that'd be a bigger announcement somewhere than what's in the release notes. 🤔

@TimvdLippe
Copy link
Contributor Author

@stephenyeargin Friendly ping on this PR 😄

@stephenyeargin
Copy link
Member

I'd really hoped for a bit of feedback from the core Hubot folks to see if the CoffeeScript deprecation was permanent/required for future work. This isn't a terribly consequential package, so I'll go forward with merging.

@stephenyeargin stephenyeargin merged commit 92d9fc6 into hubot-archive:master Jan 9, 2018
@TimvdLippe
Copy link
Contributor Author

@stephenyeargin Awesome, thanks for the quick response!

@stephenyeargin
Copy link
Member

stephenyeargin commented Jan 9, 2018

Released with v1.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants