mjolnir/tsconfig.json

{
    "compilerOptions": {
        "alwaysStrict": true,
        "esModuleInterop": true,
        "experimentalDecorators": true,
        "emitDecoratorMetadata": true,
        "module": "commonjs",
        "moduleResolution": "node",
        "newLine": "LF",
        "noImplicitReturns": true,
        "noUnusedLocals": true,
        "target": "es2021",
        "noImplicitAny": true,
        "sourceMap": true,
        "strictNullChecks": true,
        "outDir": "./lib",
        "types": [
            "node",
            "mocha"
        ]
    },
    "include": [
        "./src/**/*",
	    "./test/appservice/**/*",
        "./test/integration/manualLaunchScript.ts",
        "./test/integration/roomMembersTest.ts",
        "./test/integration/banListTest.ts",
        "./test/integration/reportPollingTest",
        "./test/integration/policyConsumptionTest.ts",
        "./test/integration/openMetricsTest.ts",
    ]
}
Absolute bare minimum for a bot 2019-09-25 22:13:20 -04:00			`{`
			`"compilerOptions": {`
Lint: Enabling 'noImplicitReturns' 2021-07-22 02:24:12 -04:00			`"alwaysStrict": true,`
manymjolnir appservice (#364) Mjolnir can now be run as an application service, meaning it will host multiple independent mjolnirs that can be requested by users. If the user is on the same homeserver as the appservice is deployed on, then they can provision a mjolnir via a widget https://github.com/matrix-org/mjolnir-widget. Otherwise they can invite the appservice bot to a room they want to protect. This will create them a mjolnir, a management room and a policy list. The appservice shares the same docker image as the bot, but is started slightly differently by specifying "appservice" as the first argument to docker run (this s managed by `mjolnir-entrypoint.sh`. We could have used another Dockerfile for the appservice, extending the existing one but we decided not to because there would have been lots of fiddling around the entrypoint and logistics involved around adding a tag for it via github actions. Not to mention that this would be duplicating the image just to run it with a different binary. A list of followup issues can be found here https://github.com/issues?q=is%3Aopen+is%3Aissue+author%3AGnuxie+archived%3Afalse+label%3AA-Appservice. Somewhat relevant and squashed commit messages(regrettably squashing because frankly these won't make sense in isolation): * draft widget backend * add `managementRoomId` to `provisionNewMjolnir` * remove ratelimits from appservice mjolnirs * add /join endpoint to api backend * tighter guard around room type in PolicyList matrix-bot-sdk imporved the types for this * enable esModuleInterop * launch and use postgres in a container whilst using mx-tester * limited access control policy list used for access control * Redesign initialization API of many mjolnir. It's much harder to forget to initialize the components now that you have to in order to construct them in the first place. * Ammend config not to clash with existing CI this means that the appsrvice bot is now called 'mjolnir-bot' by default which was easier than going through old code base and renaming * Change entrypoint in Dockerfile so that we can start the appservice. We could have used another Dockerfile for the appservice, extending the exising one but we decided not to because there would have been lots of fiddling around the entrypoint and logistics involved around adding a tag for it via github actions. Not to mention that this would be duplicating the image just to run it with a different binary. This solution is much simpler, backwards compatible, and conscious about the future. Co-authored-by: gnuxie <gnuxie@element.io> 2022-11-15 13:03:06 -05:00			`"esModuleInterop": true,`
Absolute bare minimum for a bot 2019-09-25 22:13:20 -04:00			`"experimentalDecorators": true,`
			`"emitDecoratorMetadata": true,`
			`"module": "commonjs",`
			`"moduleResolution": "node",`
Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 (#135) * Intercept /report and display human-readable abuse reports in the moderation room - Resolves #38 2021-10-07 08:42:08 -04:00			`"newLine": "LF",`
Lint: Enabling 'noImplicitReturns' 2021-07-22 02:24:12 -04:00			`"noImplicitReturns": true,`
Lint: Enabling 'noUnusedLocals' 2021-07-22 02:47:41 -04:00			`"noUnusedLocals": true,`
Update tsconfig.json touse ES2021 (#337) Node16+ allows usage of ES2021 features, and frankly ES2015 is very old now. 2022-07-26 10:33:43 -04:00			`"target": "es2021",`
enable noImplicitAny (#209) 2022-02-02 07:43:05 -05:00			`"noImplicitAny": true,`
Absolute bare minimum for a bot 2019-09-25 22:13:20 -04:00			`"sourceMap": true,`
Lint: Enabling 'strictNullChecks' 2021-07-22 02:38:44 -04:00			`"strictNullChecks": true,`
Absolute bare minimum for a bot 2019-09-25 22:13:20 -04:00			`"outDir": "./lib",`
			`"types": [`
Make the [un]ban command smarter Fixes https://github.com/matrix-org/mjolnir/issues/11 2019-11-13 23:38:19 -05:00			`"node",`
			`"mocha"`
Absolute bare minimum for a bot 2019-09-25 22:13:20 -04:00			`]`
			`},`
			`"include": [`
Fix the test script `yarn test:manual` and add it to tsconfig (#234) * Add test:manual launch script to tsconfig this is so we won't keep breaking it 2022-02-24 09:46:15 -05:00			`"./src/*/",`
Appservice tests weren't added to tsconfig.json properly. (#440) Some minor fixes now that they have been. 2022-11-28 07:55:43 -05:00			`"./test/appservice/*/",`
New command `!mjolnir since <date or duration> <kick \| ban \| show> <limit> [reason] [...rooms]` (#238) A new command `since` to affect all users who have joined a protected room since a given date. 2022-03-21 05:39:15 -04:00			`"./test/integration/manualLaunchScript.ts",`
Apply members and server bans to the most recently active rooms first. (#274) * Apply members and server bans to the most recently active rooms first. https://github.com/matrix-org/mjolnir/issues/273 2022-05-03 07:36:53 -04:00			`"./test/integration/roomMembersTest.ts",`
implement polling reports in synapse (#259) 2022-07-04 10:06:36 -04:00			`"./test/integration/banListTest.ts",`
Unbitrotting ruleserver tests (#418) 2022-11-15 07:06:41 -05:00			`"./test/integration/reportPollingTest",`
			`"./test/integration/policyConsumptionTest.ts",`
Very basic support for OpenMetrics (aka Prometheus) (#442) This PR: - creates an OpenMetrics server that enables collecting performance data from this process by e.g. a Prometheus server; - exposes as metrics the performance of http requests with MatrixBot. Further metrics may of course be added. 2023-01-05 02:37:54 -05:00			`"./test/integration/openMetricsTest.ts",`
Absolute bare minimum for a bot 2019-09-25 22:13:20 -04:00			`]`
			`}`