Dragory b47872bf87 utility: fix !clean response delete behaviour ... The !clean response is intended to be deleted after a delay when cleaning the current channel i.e. not specifying a different channel to clean. This behaviour was reversed, so the response got deleted when cleaning a different channel and stayed when cleaning the current channel.		2019-11-30 22:23:11 +02:00
..
src	utility: fix !clean response delete behaviour	2019-11-30 22:23:11 +02:00
.gitignore	Reorganize project. Add folder for shared code between backend/dashboard. Switch from jest to ava for tests.	2019-11-02 22:11:26 +02:00
api.env.example	Reorganize project. Add folder for shared code between backend/dashboard. Switch from jest to ava for tests.	2019-11-02 22:11:26 +02:00
bot.env.example	Reorganize project. Add folder for shared code between backend/dashboard. Switch from jest to ava for tests.	2019-11-02 22:11:26 +02:00
ormconfig.js	Switch from ts-node to tsc-watch for faster watch restarts; move format npm script to project root	2019-11-30 17:05:18 +02:00
package-lock.json	automod: add normalize and loose_matching trigger options	2019-11-30 22:04:28 +02:00
package.json	automod: add normalize and loose_matching trigger options	2019-11-30 22:04:28 +02:00
register-tsconfig-paths.js	Switch from ts-node to tsc-watch for faster watch restarts; move format npm script to project root	2019-11-30 17:05:18 +02:00
start-dev.js	Switch from ts-node to tsc-watch for faster watch restarts; move format npm script to project root	2019-11-30 17:05:18 +02:00
tsconfig.json	Change target in tsconfig from esnext to es2018 to support optional chaining/nullish coalescing on Node.js 12	2019-11-27 21:43:54 +02:00