the-guard-bot/bot/index.js

'use strict';

const Telegraf = require('telegraf');
const config = require('../config');

const bot = new Telegraf(config.token);

if (process.env.NODE_ENV === 'development') {
	bot.polling.offset = -1;
}

module.exports = bot;

// cyclic dependency
// bot/index requires context requires actions/warn requires bot/index
Object.assign(bot.context, require('./context'));
refactored to be more modular 2017-09-21 13:57:49 +04:30			`'use strict';`

			`const Telegraf = require('telegraf');`
Don't assume config file extension Even if we want to enforce one extension, doing it in requires scattered across the whole project doesn't sound like a good idea (don't repeat yourself). This commit also enables .js configs, so I added that to .gitignore. I'll document it when we settle on default config format. Why was .json everywhere in the first place? I thought it was neccessary in some older versions of Node to be able to require a .json file. 2017-11-24 12:31:47 +01:00			`const config = require('../config');`
refactored to be more modular 2017-09-21 13:57:49 +04:30
			`const bot = new Telegraf(config.token);`

Ignore past messages when in development 2017-11-01 20:59:27 +01:00			`if (process.env.NODE_ENV === 'development') {`
Update dependencies; closes #55. 2018-02-10 20:20:17 +01:00			`bot.polling.offset = -1;`
Ignore past messages when in development 2017-11-01 20:59:27 +01:00			`}`

refactored to be more modular 2017-09-21 13:57:49 +04:30			`module.exports = bot;`
[Bugfix] handle cyclic dependency 2018-05-05 20:10:22 +02:00
			`// cyclic dependency`
			`// bot/index requires context requires actions/warn requires bot/index`
			`Object.assign(bot.context, require('./context'));`