the-guard-bot/plugins/index.js

'use strict';

const { compose } = require('telegraf');

const config = require('../config');
const names = config.plugins || [];

const plugins = names.map(name => `./${name}`).map(require);

module.exports = compose(plugins);
Added support for plugins 2017-10-27 18:43:33 +02:00			`'use strict';`

			`const { compose } = 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');`
Added support for plugins 2017-10-27 18:43:33 +02:00			`const names = config.plugins \|\| [];`

			const plugins = names.map(name => `./${name}`).map(require);

			`module.exports = compose(plugins);`