Ensure feature parity with non-SDK features in old bot code #3
Labels
areas::processes::planning
High-level strategy and planning
areas::product::release
Affects a project in release form, as consumed by users
areas::product::source
Affects product source (code, etc)
tasks::features::new
New features
tasks::review::compliance
Alignment with standards or regulations
tasks::review::design
Setup, architecture or design patterns
tasks::review::functional
Alignment with specifications and requirements
The MVP for the Server Companion rewrite must have feature parity with the old bot.
While we've been hard at work over the past year planning and building our vNext architecture for SDK features, the bot features which don't depend on our database or SDK are simpler and can be implemented in tandem.
To that end, this document reviews and tracks the various features in our "old infra" which can be implemented now without the use of our SDK.
Existing non-SDK features
The original TypeScript code used Discord.js, but we'll be using Remora for our rewrite implementation.
We already have an end-to-end testbed setup for developers to run the bot rewrite in our test server.
Commands
The commands that need consideration can be found at uwpcommunity-backend/tree/dev/src/bot/commands. Each file is a command that can be run, and the default TS import declares the parameters.
As of a75cc7ac5bd3761aef25f4aebd869cfcd23cbce4, these are:
The only commonly used commands here are:
Of these three commands, the project command is part of our SDK, so only the infraction system and the portal command are left to be implemented without it.
Events
Events that may need implemented can be found at uwpcommunity-backend/tree/dev/src/bot/events.
As of 1cedacadb69534dc6a42d9ac24492684b2192873, these are:
Required work
Commands
The infraction system and portal command need to be implemented in the new bot using Remora.
Events
Only the swear filter and dev-chatter warning need to be implemented for now.
Details and requirements will be filed in separate tickets from here. Come back soon.
Tasks
The text was updated successfully, but these errors were encountered: