ERROR hubot-heroku-alive included, but missing HUBOT_HEROKU_KEEPALIVE_URL. ![]() WARNING Loading scripts from hubot-scripts.json is deprecated and will be removed in 3.0 () in favor of packages for each script. Hubot> INFO /Users/kon_yu/development/myhubot/scripts/ffee is using deprecated documentation syntax Warning: This is an experimental feature and could change at any time:Ĭhrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/c9bc2176-7ce4-4d18-a9eb-de23caa2790d Warning: This is an experimental feature and could change at any time. Any tips/advice?ĮDIT - Was able to get the changes from #528 and #565 working locally will provide Hubot and Coffeescript version numbers for compatibility in a bit.> HUBOT_SLACK_TOKEN=xoxb-YOUR-TOKEN-HERE coffee -nodejs -inspect node_modules/.bin/hubot -adapter slack It may be something within my code, since I can get through the hubot-adapter test example just fine until I load in my module under test, which throws this error without giving me a full stack trace when invoked via mocha, even when specifying -full-trace. It throws this error when I try to load in my_ffee but I'm not directly invoking ReactionMessage anywhere in my script. Super not familiar with Coffeescript, but I'm trying to figure out where in my script is actually invoking that, and it looks like it's doing that within either bot.coffee or my_ffee, but I don't know how to trace through the execution of a test with the debugger, so I can't walk through the code and find it just yet (I'm using Mocha/Chai/hubot-adapter). One use of super without arguments or parentheses:ĮRROR Unable to load /home/admin/hubot/scripts/my_script: /home/admin/hubot/node_modules/hubot-slack/src/ffee:21:11: error: Can't call super with in derived class constructors.It looks like there's probably only one compatibility issue, but I need to test more: □ Supported, but not compatible with hubot-slack. Hubot 2.x classes are written in Coffeescript before the release of 2.x. Compatibility testing Hubot 2.x + Coffeescript 1.x I've outlined the compatibility testing I've performed with the problems I've identified. If it doesn’t, it will set a default empty string for the token, which will cause calls to the Web API to fail (which is what we want). While Hubot 3.x is compatible with Coffeescript 2.x, since Hubot itself is no longer written in CS, hubot-slack isn't yet compatible. You can then get the token in your code simply: var token '' This will ensure that your app has a Slack token before it proceeds. This means that constructors using the attribute name/assignment shorthand must call super() immediately before doing anything else. ECMAScript 2015 requires that super always be called before attributes are read or assigned within a constructor, so Coffeescript now has the same requirement. In Slack Go to the room that you configured the integration with Hubot In the channel enter: To see the list of command you can run, you can either visit the.This means that super, when called as a method, has to be called as super() in order to disambiguate. super is now both a keyword and a method.This required two major backwards-incompatible changes in order to comply with JS class requirements: Coffeescript 2.x classes instead compile down to ECMAScript 2015 classes in order to improve interoperability with modern JS. ![]() Coffeescript 1.x's object model is a custom one which compiles down to JS prototype-based objects, since Coffeescript 1.x predates JS having its own class model. The primary incompatibility between Coffeescript 1.x and 2.x is the class type.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |